SNOW Visual Studio Code Plugin creating duplicates and destroys development

Imi NOW
Tera Contributor

Hi Community,

is there anyone experiencing issues regarding ServiceNow Plugin used within Visual Studio Code? We use Utah and last available fixes.

 

Plugin is outdated and last update was 3 years ago, it doesn't support new JavaScript engine ECMAScript 2022 ES13 or ES12 without "hacking" or tweaking plugin settings.

 

Potentionally, I can live with it but the biggest issue is creating duplicate Script Includes, Tables/Fields etc...

 

Issue happens when we develop scoped applications, 2 developers works on different script includes and after saving/syncing the project from time to time Visual Code create duplicates, e.g. the original script include is named AA_LoremIpsumDolor and after pressing sync the new one is created with different sys_id and the script name of the new one has the name AA_LoremIpsumDolor_9d385017c611228701d22104cc95c371 (or random generated sys_id).

 

We also experienced issue where existing table (x_zits2_lorem_table_null) has 3 custom fields (aa_field1, aa_field2 and aa_field3) and after syncing the original table did remain and it created 3 new tables called as per field name from initial one, e.g. x_zits2_lorem_table_aa_field1_null, x_zits2_lorem_table_aa_field2_null, x_zits2_lorem_table_aa_field3_null

 

These issues brings us a big pain during development and causes chaos within instance.

 

Is there any way how to fix it or planned date when ServiceNow release new plugin which will stick to the new standards?

 

Thank you!

 

0 REPLIES 0