Vancouver Upgrade - Skipped errors: Import translations for @now-par-components/sn-par-refresh-...

[Christian Prob2]

Hi,

just going over some skipped records with disposition "Skipped Error" with short descriptions like:

• Import translations for @NOW-par-components/sn-par-number-format (Script Action from sn_par_nbr_format)
• Import translations for @NOW-par-components/sn-par-refresh-frequency (Script Action from sn_par_refresh_fre)
• Import translations for @Servicenow/now-vis-pie (Script Action from sn_vis_pie)
• Import translations for @NOW-par-components/sn-par-scorecard-metrics (Script Action from sn_par_sc_metrics)
• Import translations for @NOW-par-components/sn-par-date-input (Script Action from sn_par_date_input)
• Import translations for @NOW-par-components/sn-par-data-sources (Script Action from sn_par_data_source)
• Import translations for @devsnc/sn-par-calendar-connected (Script Action from sn_par_calendar)

and a few more, all of type "Script Action". 

No "Resolve Conflicts" / "Revert to Base System".

Would anyone have the same issues and maybe an idea how to resolve those?

Thanks,

Christian

[Michael Wendel1]

just stumbling across the same skipped records and have no clue how to handle them?

[Mary S]

@Christian Prob2  Did you ever get an answer on how to handle these skipped records?

[Mary S]

I just heard back from ServiceNow with the following:

Found most records with the skipped reason as:

Skipping because file already exists with a different scope: <record name>

I have looked this up and found the following documentation:

• How to resolve Skipped changes with Disposition 'Skipped Error' after upgrade

The other record I have noticed reports the reason as:

Skipping attempt to set property com.snc.kmf.cert.validation.enabled to unsafe value false

For this error, I found the following:

• KMF System Property [com.snc.kmf.signature.validation.flag] is not updated after upgrading to Rome a...

Also see this post for type "Indexes" Solved: What do you do with skipped updates of type 'Index... - ServiceNow Community

[Roman88]

It seems like you are encountering issues while attempting to import translations for various Script Actions in ServiceNow, and you are seeking help in resolving these errors.

Here are some potential steps to troubleshoot and resolve these translation import errors:

1. Check Data Integrity:
Review the data being imported to ensure that the translations are in the correct format and structure expected by the import process. Verify that there are no formatting or syntax issues in the translation files.

2. Script Action Configuration:
Ensure that the script actions referenced in the error messages are correctly configured in ServiceNow. Check if the referenced script actions exist and are linked to the appropriate components within the platform.

3. Review Error Logs:
Access the error logs or import history in ServiceNow to gain more detailed information about the specific errors encountered during the translation import process. This can provide insights into the root causes of the issues.

4. Support Documentation:
Refer to ServiceNow documentation, specifically regarding the localization framework and translation import process. The documentation may contain specific troubleshooting steps or common error scenarios with their respective solutions.

5. Engage ServiceNow Community:
Consider reaching out to the ServiceNow community, forums, or support channels to seek assistance from other users or ServiceNow experts who may have encountered similar translation import issues and can provide guidance or solutions.

By following these steps and leveraging available resources, you may be able to diagnose and resolve the issues related to importing translations for Script Actions in ServiceNow. If you have specific error messages or details from the logs, providing them could help in offering more targeted assistance. Visit here