Transform Fails on Sync with "ImportDeclaration" vs "ExpressionStatement" Mismatch

[shaumik100x]

When attempting to synchronize our application to a local environment using the Fluent-based ServiceNow SDK, the now-sdk transform process fails consistently. The error message indicates a syntax mismatch during the transformation of certain records: Transform failed Unexpected! Inserting syntax kind of ImportDeclaration, but ExpressionStatement was inserted.

This error is problematic because it halts the entire synchronization process. Even a single problematic record prevents the entire application from being synced locally. This significantly disrupts our development workflow, as we are unable to pull down the latest changes and work on our application in our local development environments.

The current behavior of failing the entire transformation for a single record error is not ideal. A more resilient approach would be to log the error for the specific record and continue with the transformation of the remaining records.

[now-sdk] ERROR: Transform failed Unexpected! Inserting syntax kind of ImportDeclaration, but ExpressionStatement was inserted.

    at ServiceNowDevelopmentService.startDevelopment (lib/servicenow/development.ts:722:14)
    at async POST (app/api/development/start/route.ts:9:19)
    at async startOrResumeDaytona (lib/daytona/server.ts:32:21)
    at async POST (app/(chat)/api/chat/route.ts:886:25)

We would like to request an enhancement to the transform process. Instead of failing the entire synchronization due to a single record's transformation error, we suggest the following behavior:

• Log the error: Clearly log the error for the specific record that failed to transform, including the record's sys_id and table.
• Continue the process: Continue the transformation process for the remaining records in the application.

This would allow developers to continue their work and address the problematic record individually without a complete halt in the development workflow.

[venkat-kaluva]

Hi @shaumik100x,

Thanks for your feedback. We are working on enhancing the transform functionality., and we hope that would resolve this issue.

Can you share a small sample app with minimal code for reproducing the issue ? if you could share the type of record that's failing we can take a look.

[shaumik100x]

It's a little hard to give the type of record that caused that failure because the error message doesn't really give much information.
sys_remote_update_set_3cd60998831aea50b02ac430ceaad33a.xml.txt
Here's similar one that gives a different error:

[now-sdk] ERROR: Errored during transformer on file:
[now-sdk] ERROR: Transform failed Cannot find a step matching config with id: 84e977b05330220002c6435723dc3410

but this one gives a better error

[shaumik100x]

sys_remote_update_set_950e19909352ae50195dfb579803d662.xml.txt

This update set that caused the initial error

[venkat-kaluva]

I will debug that and see what's going on. Thanks for sharing the updateset

[venkat-kaluva]

@shaumik100x, the ,first update set is missing the sys_atf_step_config record with the sys_id in the error message. We will improve the log message to include the table name for easy debugging.

I was unable to load the second update set due to missing records like the sys_app and more

[shaumik100x]

Okay thank you. I'll try to get a better update sets to reproduce this.