I renamed a property value and now Switch is saying:
"Requested property value is not defined: 'PrivateDataValue1'; trying to use default value"
I renamed PrivateDataValue1 to Value1 and nowhere in my code does it reference PrivateDataValue1.
It runs fine in SwitchScripter but errors out in Switch.
I tried reloading the script, remaking the property values, putting the script in a new flow. I have no idea what is going on here...
Frustrating bug
Frustrating bug
Free Switch scripts: open-automation @ GitHub
Free Switch apps: open-automation @ Enfocus appstore
Want to hire me? I'm looking for my next gig. Contact me on LinkedIn or via email.
Free Switch apps: open-automation @ Enfocus appstore
Want to hire me? I'm looking for my next gig. Contact me on LinkedIn or via email.
-
- TOP CONTRIBUTOR
- Posts: 658
- Joined: Mon Nov 29, 2010 8:45 pm
- Location: Alpharetta GA USA
- Contact:
Frustrating bug
If you are using Switch 12 you have to restart Switch Server to get it pickup script changes.
Another problem we have discovered in Switch 12 is importing a flow with scripts will use an existing potentially older script if it's in the same location as the system you exported flow from. It creates a new script when you imported it but doesn't automatically reload it so properties and input/output connections may be wrong. Always reload your scripts after importing a flow.
Another problem we have discovered in Switch 12 is importing a flow with scripts will use an existing potentially older script if it's in the same location as the system you exported flow from. It creates a new script when you imported it but doesn't automatically reload it so properties and input/output connections may be wrong. Always reload your scripts after importing a flow.
Frustrating bug
dkelly wrote: If you are using Switch 12 you have to restart Switch Server to get it pickup script changes.
Another problem we have discovered in Switch 12 is importing a flow with scripts will use an existing potentially older script if it's in the same location as the system you exported flow from. It creates a new script when you imported it but doesn't automatically reload it so properties and input/output connections may be wrong. Always reload your scripts after importing a flow.
Thanks man... that was really driving me crazy!
Another problem we have discovered in Switch 12 is importing a flow with scripts will use an existing potentially older script if it's in the same location as the system you exported flow from. It creates a new script when you imported it but doesn't automatically reload it so properties and input/output connections may be wrong. Always reload your scripts after importing a flow.
Thanks man... that was really driving me crazy!
Free Switch scripts: open-automation @ GitHub
Free Switch apps: open-automation @ Enfocus appstore
Want to hire me? I'm looking for my next gig. Contact me on LinkedIn or via email.
Free Switch apps: open-automation @ Enfocus appstore
Want to hire me? I'm looking for my next gig. Contact me on LinkedIn or via email.
Re: Frustrating bug
I still run into this all the time and its very frustrating. We have to restart our entire production Switch server to load in a small script change.
Free Switch scripts: open-automation @ GitHub
Free Switch apps: open-automation @ Enfocus appstore
Want to hire me? I'm looking for my next gig. Contact me on LinkedIn or via email.
Free Switch apps: open-automation @ Enfocus appstore
Want to hire me? I'm looking for my next gig. Contact me on LinkedIn or via email.