tkapitan / alrm-businesscentral Goto Github PK

TKapitan/ALRM-VSCode#4

The name is slightly confusing, could be something like Create License Object Range CSV file, bot no biggie there...

What could be slightly improved though is to ignore custom object ranges that already exist in the license files and can't be changed - so no point in assigning them from the available objects to be assigned. (50000..50009 for tables and 50000..50099 for other object types excl. codeunits).

Maybe an omit range parameters for tables, pages, reports, queries, xmlports with savevalues on would do it.

TKapitan/ALRM-VSCode#12

Extension Usage list has duped "Starting date" in CZ. Propably just wrong translations, but tooltips are the same as well.
Lines also cannot be renamed - error is thrown when changing starting date. (Feature?)

There are some invalid characters that cannot be used within extension name (such as ":")

ALRM: New Object assign ID for Enmu. ID is assigned in BC but not in the VS Code.

Make Code for Assignable Ranges NotBlank

This will break features like transferfields and others.

Add report to show how many tableextension with new fields are created per the same table per extension usage. This can help to identify problems with designed solutions (many tableextensions on the same table)

Currently you can create multiple extension usage entries for one instance code. This can break the export procedure.

Check permissionset name - maximum length is 20 characters.