Implement an Interface in AL to extend a Business Central App in AppSource

[@sureshbhat6937]

Thanks Erik for this wonderful information.

[@itslissi]

Hey Erik, thank you so much!

[@klauskaan6320]

It is pretty cool actually! I completely agree with this statement!

[@TeChWarZ]

Thank you for this video!

[@sameervirmani9159]

Hello Sir, thank you for your videos. I have slightly different question. This is with regards to Business Central Dual Use rights license policy. As per Microsoft the partner can download. Flf file for the customer and use the business central on premise. It means the same subscription model can be used for on premise and cloud too. You know do we have to buy object range when using business on-premise for the customization development in object range of 50000 to 99999? As the same is not required for BC SAAS version.

[@Hougaard]

Not required for dual use right license.

[@sameervirmani9159]

@@Hougaard thnkx appreciate your prompt reply

[@guidorobben6259]

Nice and simple!

[@XdimidrolX]

Hey Erik! How about handling the codeunit dependencies via interfaces, can you imagine that one version of BC has a certain codeunit but another not, could it be possible to create generic app compatible with both BC versions, so handle codeunit dependency using the interfaces?

[@Hougaard]

That would require at least three different extension to get the dependency model to work...

[@XdimidrolX]

@@Hougaard What do you mean? Could you clarify please?

[@klauskaan6320]

I want whatever video you might suggest!

[@preetgor422]

👍

[@chriswatson2407]

Have you tried an eventless model whereby in source app you merely execute the required method against an instantiated interface variable? Causes Mongocodeunit.method to execute. Works okay for me.

[@tetraquark2402]

That's actually how I thought it should work