Describe the issue
As a developer
I want to upload multiple Word body layouts to dev scope in a single
operation
so that I don't have to wait for one publish per layout when working
on a report package containing many layouts.
Observed behaviour:
When publishing to dev scope from VS Code with several report layouts
in the extension, the layouts are sent one at a time. Each layout
triggers its own upload operation, and the next layout does come into Report Layouts until we run the deployment once mrore
Impact:
- Long feedback loop for layout work, where the whole package must be
republished to test a single change
Environment:
- VS Code version: [to be filled in]
- AL Language version: [to be filled in]
- BC version / sandbox type: [to be filled in]
- Number of layouts in the package when observed: [to be filled in]
- Measured publish time: [to be filled in]
Expected behavior
Layouts are uploaded together (batched) as part of a single publish
operation, or at minimum in parallel, so that publish time does not
scale 1:1 with the number of layouts.
Steps to reproduce
- Create/open an AL extension with N report layouts (Word body files)
registered in the rendering section
- Publish to dev scope from VS Code (F5 / Publish without debugging)
- Observe the upload sequence — layouts are sent sequentially
Additional context
No response
Describe the issue
As a developer
I want to upload multiple Word body layouts to dev scope in a single
operation
so that I don't have to wait for one publish per layout when working
on a report package containing many layouts.
Observed behaviour:
When publishing to dev scope from VS Code with several report layouts
in the extension, the layouts are sent one at a time. Each layout
triggers its own upload operation, and the next layout does come into Report Layouts until we run the deployment once mrore
Impact:
republished to test a single change
Environment:
Expected behavior
Layouts are uploaded together (batched) as part of a single publish
operation, or at minimum in parallel, so that publish time does not
scale 1:1 with the number of layouts.
Steps to reproduce
registered in the rendering section
Additional context
No response