We have adopted an AL development strategy where we see an AL extension as a module.

This has resulted in great productivity and maintainability in our large development team.

Our marketing department does not like the idea of having a lot of apps showing on appsource, they prefer apps to be bundled into solutions that show up on appsource.

Currently the only way of meeting this requirement is to create an app that only has a app.json that combines our modules into a single offer on appsource.

But we are now running into limitations of the BC service and related infrastructure. In a support case we got to know that the AVS appsource submission system is no longer capable of handling our submission.

A 30 apps bundle for 42 target countries results in 7500 tasks within AVS .

Idea: Have a feature at the appsource level that allows our sales/marketing people to combine multiple apps into an offer without the need for an extra app + dependencies. That way they can also manage the bundle independent of the release cycle of the actual apps. If sales is happy, everyone is happy

More details below:

Root Cause Analysis

The submission exceeded AVS's 30-minute CreateSubJobs timeout due to combinatorial complexity.

Per official AVS documentation: "AVS creates tasks in proportionality to the amount of apps, resolved releases, and target countries."

Factor

Value

Apps in submission

~30 (Our bundle)

Target countries

42

Resolved releases

6 (27.0 - 27.5)

Estimated tasks

~7,500+