Skip to main content
Question

Language issues with connections

  • Aug 19, 2024 5:02 PM UTC
  • 6 replies
  • 342 views

Forum|alt.badge.img+1

I see this was a problem previously but I am experiencing this with my first connection. When you select create a card the field options are in Portugese. Both my pipes are in English. Any suggestions? 

6 replies

marcosmelo
Forum|alt.badge.img+18
  • Legend
  • Aug 19, 2024 6:28 PM UTC

Hi

 

I suggest contacting support


Forum|alt.badge.img+1

I deleted connection and restarted process, logged off, logged back in and now it is in English so I think I am ok. 


marcosmelo
Forum|alt.badge.img+18
  • Legend
  • Aug 19, 2024 8:49 PM UTC

Very good!!


  • Explorer
  • Aug 31, 2024 10:18 AM UTC

It sounds frustrating to have the field options in Portuguese when everything else is set to English. This could be due to a localization setting that didn’t carry over properly. I’d suggest checking the language settings within your account preferences or looking for any default language options within the "Create a Card" settings. If that doesn’t work, sometimes clearing your browser cache or trying a different browser can help reset those settings. Hopefully, this helps get things back on track!


  • Explorer
  • Sep 1, 2024 9:55 AM UTC

"It sounds frustrating to have the field options in Portuguese when everything else is set to English. This could be due to a localization setting that didn’t carry over properly. I’d suggest checking the language settings within your account preferences or looking for any default language options within the 'Create a Card' settings. If that doesn’t work, sometimes clearing your browser cache or trying a different browser can help reset those settings. For more detailed advice or support, you can check out Konferensbokarna. Hopefully, this helps get things back on track!"

 


Rodrigo Farias
Pipefy Staff
Forum|alt.badge.img

Hi team, maybe at some point the field was created with the language set to Portuguese, I did a test and got this behavior. Deleting the field and creating it again with the correct language is the solution.