You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My team have been using AL Object ID Ninja VS Code extension connected to our own Azure back-end for over a year now, until it stopped working, and we started getting the following error notification:
This error shows up after we create a new .al file and start typing object type and a space - i.e. when the extension is expected to call the API. I am not entirely sure when it stopped working due to summer/vacation period, so I cannot say 100% when exactly this became a problem, e.g. how long after the VS Code extension was updated to the newest version by the team members.
As far as I know there have not been any changes to the deployed Azure functions, and I double checked the security keys. Tested with a newly generated pair of keys, but got the same error. Deployed the newest version from GitHub (downloaded today - commit e6d721f, v2.11.1), same same.
Using AL Object ID Ninja - VS Code extension v2.11.1.
I am not sure whether it is an issue with the product, or with our infrastructure/setup, but I would appreciate any tips on how to fix it.
The text was updated successfully, but these errors were encountered:
My team have been using AL Object ID Ninja VS Code extension connected to our own Azure back-end for over a year now, until it stopped working, and we started getting the following error notification:
This error shows up after we create a new .al file and start typing object type and a space - i.e. when the extension is expected to call the API. I am not entirely sure when it stopped working due to summer/vacation period, so I cannot say 100% when exactly this became a problem, e.g. how long after the VS Code extension was updated to the newest version by the team members.
As far as I know there have not been any changes to the deployed Azure functions, and I double checked the security keys. Tested with a newly generated pair of keys, but got the same error. Deployed the newest version from GitHub (downloaded today - commit e6d721f, v2.11.1), same same.
Using AL Object ID Ninja - VS Code extension v2.11.1.
I am not sure whether it is an issue with the product, or with our infrastructure/setup, but I would appreciate any tips on how to fix it.
The text was updated successfully, but these errors were encountered: