Hello, everyone,

We discovered a missing functionality between an AppSource extension and dependent PTEs. When a change is triggered over AppSource extension, for example obsolete a field or renaming a field, the AppSource validation process runs smooth and the App is published, however, the PTEs that depend on the given fields, names etc, will not work properly due to the prior change in the App.

Once the AppSource extension is updated in a given tenant, the PTEs could work correctly:

1. Obsolete field will be missing in the dependent PTE.
2. Renamed field won't be editable.

Our request is to have an agent, which can detects the changes in the AppSource extension (once we update it through TAC) combined with dependent PTEs to detect it and a message to be displayed/email to be send which will inform users that dependent PTEs won't be compatible and to seeks assistance from Partner/Administrator"

Thank you for considering this idea!