Challenge #1: App doesn’t refresh instantly

Challenge #1

When a change is made in an embedded canvas app, it needs to be published before you can see the changes within the model-driven form. That being said, once a change is made and the app is published, refreshing the model-driven form may not reflect the recent changes. Sometimes, you have to refresh the model-driven app multiple times for the changes to reflect. This can give false impressions especially when you make some changes to the code to fix an issue with the app. Seeing the issue persist might lead to a false impression that the fix did not work the way it should have.

Trick #1

While there is no way to ensure the app gets refreshed instantly, one simple best practice can go a long way in ensuring that you know for sure your changes are getting reflected. Add a label in the header or footer or anywhere on the 1st screen of the app with the text "v 1.0" (or any other text that denotes a version number). Make sure you update it every time you make a change and publish the app. Then when you refresh the model-driven app, checking the version number can be an easy confirmation as to whether the version you are seeing is the latest or not.

Have fun! Get addicted!