tkapitan / alrm-vscode Goto Github PK

Looking at the extension object table. When I use Synchronize, the "Extension ID" field is always an 'empty' GUID ({00000000-0000-0000-0000-000000000000}) and the 'Extends Object Name' field for page/table extensions (I don't have any other types of extension in the apps right now) is also empty.

Is this intentional?

If no tenant is specified, the API URL is wrong (the first character is & not ?)

TKapitan/ALRM-BusinessCentral#4

Add support for multicompany BC environments

Idea for a new command: "ALRM: Add dependency"

• Can be used as a shortcut for filling in properties like appid, newest version, ...
• Would show the user list of 80000 "C4BC Extension Header"
• Publisher and newest app version would have to be stored, for example with ALRM: Synchronize (name and app id already are tracked I suppose)
• Could be later used for tracking dependencies in BC, if there were to be a need for it

#16

It would be nice to have snippets available. For example trmfield. The snippet could generate the same code block as the command does now.
It would even simplify the creation of new objects. Just create a new file manually in the right place and then use a snippet like trmtableext. Again the same code block would suffice, only problem would be registering the object's name, but the snippet could maybe trigger the same input box as the command does.

Trying to synchronize an app with the command "ALRM: Synchronize"

Getting an error

the dotnet.al file has the following structure:

dotnet
{
.
.
.
}

Allow choosing which snippets will be used for object/field creation. Allow choosing between Microsoft and Waldo snippets.

I created new TableExtension and PageExtension with ALRM New Object function, but after synchronize there was error. I tried to generate another objects ID but i had same problem. I checked if there is any duplictiny in Extension preview lines with objects, but object with same ID did not exist.

Add support for OAuth 2.0 authentication

Idea for new commands - "ALRM: Delete object" and "ALRM: Rename object".

At this time, when a users want to change the name of the object, they have to rename it both in the vscode and in the BC, so there arent any conflicts during synchronization, or delete it in the business central and synchronize to create it again with the new name.

The functions could delete/rename the object locally, while also sending the information into the BC.

Some of the snippets contain variables in lowercase, some in camelcase.
The replace function should be case insensitive so it is not necessary to define it with the right case.

First issue: TKapitan/ALRM-BusinessCentral#6

When initializing a workspace I get this prompt.

What is expected here? It does not seem to want to take anything I enter.

Not possible to connect to API in BC with different tenant from default

Check duplicate table/page extensions in the same project.

Add support for multicompany environment (so let user choose the company in VS code setting)

Controladdins should be registered (name only)

ALRM assign ID. in BC is corect name. BUT In VSCode extension name is "MyExtension" and not the one, which is in the BC.

Trying to synchronize an app and getting this message:

This app is a member of a multi-root project.

The implication is that my folder has to be named "src". Why? Can it not just use to folder containing the app.json?

Trying out the synchronize function and it runs but says successful and fails at the same time.

Any thoughts? I understand it is beta. I am trying to synchronize the ALRM extension.

The failure message is:

Synchronization of A00004 has finished with errors:
;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: aba92bca-e01f-4aef-827f-f8a418c67d82.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: c8ebdb39-d170-4724-b5de-2a8baf1dbaa3.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: cc8a17fc-d9e5-4fb7-b848-4ab3f013165e.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 261eb7a7-7ecf-43eb-9607-1e123670d55e.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: db3bcdf4-9267-4a5a-8a68-6be435a046b2.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 073c5e8c-a821-4b4f-82c4-acaad2b218e0.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: a4302498-2855-4f70-84ea-20f294016521.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 3c541366-1fb8-4261-8365-4026c4e53156.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 859d9c93-fe6c-43ad-92c0-d02e78b2d10d.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 2e863799-2ec7-442e-a256-b5a213d7fd5e.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 2cc410c2-13c6-4e01-a011-9dcb6b916ccd.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 26c5ac5a-ed34-4893-89cf-c13e98f801e9.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 54a3a936-ccba-4c6f-8071-fe321b944f59.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: ef9dce0d-7a01-40d7-a991-b07e6b90d39b.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 9c2d7fc3-ef99-4641-ba04-8b39f15468b4.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 3175d655-7008-4f4b-b6a7-66918e4ff084.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: b02b92b0-288a-45f3-8569-8a7c4ba94ea4.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 2f4e44fd-fd06-48eb-81e3-96885448d506.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 931ba157-d633-47d9-9ad3-d52384bc6591.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 1c4712c1-db85-4db6-8adb-d9b1d4bb1265.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: b05cf102-69c1-4db7-9fbd-57780f16a735.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: e40a0ef6-3971-4dc3-add8-6dbe29f2f191.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 06e2e23d-749f-48cc-8a9b-4606d451e1aa.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 9daa5f28-46b2-4cbb-92f1-b62895fd1cb8.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: b996e4ae-455d-4c2c-b5b3-c3422311b2f2.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: 0a4a72fd-1ff1-4ea6-a6f3-94298001242c.;
Error: There is no Extension Usage within the filter.

Filters: Extension Code: A00004, Starting Date: <=05/19/21, Ending Date: >=05/19/21|'' CorrelationId: dd45dc71-0b8d-49e7-949b-804fbdc28061.

Assignable Range info

VSC Extension Verison: 0.4.2

Default assignable range should be first in selection when a new extension is initialized.

Allow to update extension details in BC for already initialized extension

Add description of assignable range when new extension is initialized

Dotnet AL objects are not identified - should be skipped