@GB Thanks for reaching out. If you change your assembly, you must also update your map whether or not the map has changes as mentioned in the Note section here. Please update your map and let me know if you still observe the issue.
integration account caching assembiles
GB
1
Reputation point
Hi all,
Seems azure integration accounts cache assemblies so when trying to replace an existing one with an updated copy the maps still use the old version. Only way I can seem to get around this is by creating an entirely new dll with new namespace etc... Is this a know issue and how can you force the maps to use the latest copy, not a version in a cache?