Custom Snap Pack versioning is broken?
I have a custom snappack (version = 1, sl_build = 42) deployed in my organization’s shared folder that is in used by multiple projects. I have developed a completely rewritten version of the snappac...
Forum Discussion
@ptaylor thanks.
The other clue that I can give you is that if I change the new version numbers from 2 back to 1 and redeploy like this, everything works fine. I know the new version is picking up the new Account version because I have extra data in the new account version that the snaps depend on for “suggestions” and the suggestions are working in this configuration.
If I clear out everything and switch the version numbers back to 2, it doesn’t work.
Robert,
I can confirm that I’m seeing some errant behavior along the lines of what you’re describing, where the older version of the code appears to be executed instead of the newer code. I’ll create a defect ticket in our ticket system with a workable example.
For now, it sounds like you can work around this by keeping the version number at 1, correct?
Patrick
