Skip to content

Releases: TKapitan/ALRM-VSCode

Fix for BC RunTime 10

03 Dec 08:33
d9b0be9
Compare
Choose a tag to compare

Fix for (#31): Only the oldest object types are shown when Runtime = 10.0

New command "Switch Object IDs", Waldo's snippet fix

03 Dec 08:32
d9b0be9
Compare
Choose a tag to compare

Date of release: 27/06/2022

Major changes

  • Beta version of 'Switch Object IDs' command to be able to change ID ranges for all objects (for example PTE-ONPREM range vs. CLOUD-ONLY range)

Fixes

  • Fix links to some snippets in Waldo's extension
  • Node.JS version update

Waldo's snippets, support for more snippets for the same object type, some smaller improvements

14 Aug 21:54
Compare
Choose a tag to compare
  • Users can choose which snippets to use. Till now, the standard snippets were only available. With this update, standard snippets are default snippets but users can choose snippets made by Eric 'Waldo' Wauters, https://www.waldo.be/ instead (must be installed in the VS Code environment).
  • Add support for multiple snippets for the same object type (for example page extension has more than one snippet - for card, list, ... page types). If more snippets are found, users are asked to choose which snippet wants to use.

Other changes

  • Set IgnoreFocusOut for New Object command. With this setting the command will not be canceled when changing focus outside of the VS Code.
  • New Object command was refactored to fix focus loosing if the whole process took longer than expected.
  • BaseURL setting (deprecated since 2021/Q1, marked to be removed in 2021/Q3) was removed.

Warning message for older API versions, trim for ALRM synchronize, case-insensitive snippet replacement function, some other small improvements

23 Jul 19:32
Compare
Choose a tag to compare

Fixes

  • Reflect change of "Report Extension" snippet - the object name variable was renamed by Microsoft (See Issue #26).
  • Add an error message to extension initialization when no assignable range exists (See Issue #24).
  • Snippet variable replacement function is case-insensitive to avoid problems with changes in snippet format (See Issue #15).
  • Trim white spaces from object type, name and id during ALRM: Synchronize (See Issue #22).

Other changes

  • New warning message when some of older API versions is used (checking during VS Code extension initialization).
  • Remove setting 'Assignable Range = Do Not Use/API', the API is the only supported way now & in the future.

Fix to no tenant APIs, Support for Multi-company BC environments, some minor improvements & bugfixes

10 Jun 16:53
Compare
Choose a tag to compare

Fixes

  • Wrong API URL if no tenant is specified (See Issue #20).
  • When Synchronize command fails, both success and failure messages are shown (See Issue #18).

Other changes

  • Added support for multi-company BC environments (new setting "Company Id" that is used to build proper API URL) (See Issue #11).
  • ALRM: Synchronize command is no longer beta version.
  • Examples of both on-premises and cloud API URLs were added to the README.

Quick fix for Enum object to fill ID variable in snippet

10 May 22:35
Compare
Choose a tag to compare

Fixes

Support of API v1.1; Extension initialisation improvements, bugfixes, some other smaller improvements

10 May 08:02
Compare
Choose a tag to compare

Major changes

  • Added support for v1.1 APIs; the default version is still v1.0 (user can change API version in VS Code Setting).
  • If the v1.1 API version is selected, the name of an extended object using the newly created extension object type is synchronised to BC. The name is synchronised only during synchronisation (not during the creation of a new AL object).
  • When the new extension is initialised, the list of available assignable ranges contain more description loaded from BC API (See Issue #12)
  • Default assignable range (info loaded from assignable ranges API) is now shown as a first item during extension initialisation (See Issue #14).
  • The processing of API calls was refactored. It is possible to select (by the user directly in VS Code setup) which API version should be used. The API versions are implemented using the default interface, and the newer version extends the older ones.

Other changes

  • It is possible to connect to BC hosted on different tenant from default. User can specify tenant directly in VS Code Setup. (See Issue #7)
  • Fix of error message when the API base URL not found (See Issue #5)

New supported object types, AL files parsing improvements

02 May 20:19
Compare
Choose a tag to compare

Changes

  • The dotnet file (AL dotnet object type) does not cause synchronization error anymore.
  • Add support for Control Addin object type.
  • Improvements to parsing AL files for fields/values in table or enum extension
  • Commented fields/values are not synchronized anymore (which could cause an error during synchronization when the field/value definition was not correct)
  • AL file parsing is now case-insensitive (so object defined with first capital letter is not causing an error now).

New command: "ALRM: Synchronize", New supported objects, Preparation for BC2021W1, New validations and many small improvements

13 Mar 14:26
Compare
Choose a tag to compare

Major changes

  • New command "ALRM: Synchronize (beta)"
  • Modified command: "ALRM: New Object"
    • Users are now able to select only object types that are available for the project runtime (based on runtime setting in app.json)
    • New Validation: the object name must be max 30 chars long
  • New supported object types: PageCustomization, Profile
  • New supported runtime: Business Central 2021 W1
    • New supported object types: ReportExtension, PermissionSet, PermissionSetExtension, Entitlement
  • Changes to required API background
    • Microsoft.NAV.createObjectFieldOrValue for obtaining field IDs in "ALRM: New object extension field or value" command. Replace old command Microsoft.NAV.createObjectLine that is not called anymore).
    • Microsoft.NAV.createObjectFieldOrValueWithOwnID for registering existing fields (with already assigned field/value ID) using "ALRM: Synchronize (beta)" command.
    • Microsoft.NAV.createObjectWithOwnID for registering existing objects (with already assigned object ID) using "ALRM: Synchronize (beta)" command.

Other changes

  • Restructuralization of objects & refactoring of objectType definitions and setting
  • Fixed calls of APIs that has no return body
  • Fixed of exception when no available IDs for fields/values error was returned from API
  • Extended values loaded from app.json by runtime, platform and application
  • Some minor refactoring and minor bug fixes

Add Support for Interface object type, small refactoring

03 Jan 11:08
Compare
Choose a tag to compare
v0.2.4

Merge branch 'master' of https://github.com/TKapitan/ALRM-VSCode