The previously accurate state codes I was showing on my SKUID-ified Contact layout now gives me random (seemingly Italian) state names instead of the correct USA states.
However, when editing the picklist, the correct value is shown:
This is confusing my users greatly, any advice on how to deal with this would be appreciated.
I am working with a customer who sees this issue when viewing the State/Province Code through another object (like showing a related Account’s State/Province Code on a Contact detail page). I am not seeing this in a field editor.
One thing that you should check is that you have added the ‘MailingCountryCode’ field to your field editor. Make sure that it has ‘United States’ showing. If this field is not set, then the ‘MailingStateCode’ will not show the right value.
I wanted to update my comment. In my developer org., I have enabled State and Country Pick Lists. I am seeing the same issue as you.
I have a list of Accounts in a table. The ShippingStateCode field shows as province in another country even though I have the ShippingCountryCode field set to ‘United States’. I have Skuid 11.0.3 installed.
I did include the StateCode and CountryCode fields in my field editor. This was working fine a couple of months ago, so I suspect either Salesforce or Skuid came out with an update that disrupted this.
I enabled State and Country picklists at the beginning of this year, and was able to use them properly in Skuid.
I have 11.0.1 installed, and based on your experience, it doesn’t sound like updating will fix this problem. Hoping for an official response soon.
I did recently update to 11.0.1 at the beginning of this month, but I did that hoping it would resolve this issue. I’ve been experiencing this for at least 3 months now I believe. Do you have any idea what may be causing this?
I’m trying to reproduce the issue now. If I can, I’ll then try to do the same in other Skuid versions. Salesforce also pushes frequent maintenance releases of their own, so we don’t know yet what has changed. If you can pinpoint when this issue first surfaced for you, that will help in investigating the cause.
Were there changes to your org’s settings, or the Account fields & settings that may have had an effect? I know Bill is seeing the same issue, but I’m looking to rule out as many possible causes for the issue as I can.
Hi Eulogio and Bill, I can see the difference in performance between an org using Skuid 11.0.1 and an org using 9.5.6. Version 9.5.6 is behaving as expected, while it seems that 11.0.1 is rendering a state code without referencing its country code for context. More investigation will need to happen to pinpoint what has changed, but I will share this with our development team. We will update this conversation once we have more information, or a fix has been made available. Thank you very much for surfacing this issue.
This is an issue that our engineers are currently working to resolve in a future release. I don’t have a timeframe for you yet, but I will keep you posted on this topic as more information is available. I will pass along the information that your production environment is affected.
Thank you for your patience. A fix for this is scheduled for our next maintenance release, and we’ll be sure to update this conversation to confirm when it’s available.
Thank you for pointing this out. The release notes for 11.0.6 did list the second bullet point, referencing a fix to this issue. However, the fix for this issue was actually present in Skuid release 11.1.1, not 11.0.6. Both versions were released concurrently this week. We apologize if this was misleading, and we’ve corrected this information on the release notes page. Please feel free to give 11.1.1 a try in a non-critical sandbox to verify resolution.
As a reminder, Salesforce does NOT allow reverting back to prior versions of managed packages. Skuid always recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment. We also recommend that you update out of date themes when you upgrade. Please let us know if you continue to encounter any problems with this issue after upgrading.