At Directions EMEA I had a chat about "conditional dependencies". In my case I do have localized version of my app, due to the fact, that MS is publishing different code with the same AppId for various countries. If I now want to offer an addon to those localized apps, I do have to create multiple apps with different dependencies, depending on the localization. In general It could be solved with an Connector/ Bidge extension, but this wil cause a lot of addition effort just to maintain the AppSource offerings. So conditional dependency resolve is something I would like to see in future. Maybe there could be something like "If an app A is installed, also define a dependency to app B." App B is a library extension, that acts a a bride extension. Just somthing that came to my mind right now. One thing I don't like about your solution is that there are no warnings for discontinuations/obsoletions or type mismatches. So the user might run into runtime errors.
You could extend further by only permitting your example code to run if the dependant app is installed though I haven't got any 'app detection' code to show you.
Can we not create a custom connector app to bridge the 2 apps (Sharepoint App and the app you are trying to connect with SharePoint)? The custom connector app will have 2 dependencies and none on our Original App.
At Directions EMEA I had a chat about "conditional dependencies". In my case I do have localized version of my app, due to the fact, that MS is publishing different code with the same AppId for various countries. If I now want to offer an addon to those localized apps, I do have to create multiple apps with different dependencies, depending on the localization.
In general It could be solved with an Connector/ Bidge extension, but this wil cause a lot of addition effort just to maintain the AppSource offerings. So conditional dependency resolve is something I would like to see in future.
Maybe there could be something like "If an app A is installed, also define a dependency to app B." App B is a library extension, that acts a a bride extension. Just somthing that came to my mind right now.
One thing I don't like about your solution is that there are no warnings for discontinuations/obsoletions or type mismatches. So the user might run into runtime errors.
You could extend further by only permitting your example code to run if the dependant app is installed though I haven't got any 'app detection' code to show you.
The sound in this video does not seem to be synchronous with the pictures. Do you also get this behavior?
Windows 11 is screwing with my microphone :(
Can we not create a custom connector app to bridge the 2 apps (Sharepoint App and the app you are trying to connect with SharePoint)? The custom connector app will have 2 dependencies and none on our Original App.
Totally, but with appsource we don't have a good delivery mechanism for "minor" apps...
I have always the same problem with stream direction :D
Erik what would happened if there is no codeunit(749***) or table id 749**? a run time crash? thanks
I have done this a few times, but always feel like I am cheating :)