5/9/2024 0 Comments Scriptcase no data from tableIndicating that most of the records imported had not actually changed. Under System Import Sets > Progress, expect to see an import with a Total count that is very high with a Skipped count that is also very high - this is found under the Message column. Symptoms: The import set takes longer than expected. Repeatedly importing data that has not changed leads to many skipped rows.īecomes an issue: When a customer is importing data from a table that is very large and most of the records are not getting updated on a regular basis. How to avoid this: Use base system functionality whenever possible instead of writing custom scripts and if you do write scripts, avoid writing complicated scripts that use GlideRecord queries. Depending on the script, the entire instance may be slow during that time. Symptoms: The transform takes much longer than would be expected. GlideRecord queries typically slow down the import. For example, you can script case-sensitive coalesce instead of writing scripts that use GlideRecord queries. In most cases, script goals can be accomplished using built-in functionality within the Import Set application. This issue may appear when the transform script is not efficient. Using multiple GlideRecord queries or large loops may slow down transform scripts.īecomes an issue: When the transform scripts are using multiple GlideRecord queries or looping through large collections of objects for each row. To disable these items from running and to cease auditing and field normalization within the transform map for that import, deselect the Run business rulescheck box.Ĭonsider using an onComplete transform script to run business logic such as calculations at the end of an import rather than on each record as business rules do. For example, when importing all data from an old system, you may not want notifications to run. How to avoid this: Do not run items like business rules, workflows, approval engines, and so on during a transform unless you want all insert and update business rules, notifications, and workflows to run. Also, the entire instance may be slow during that time. Symptoms: The transform takes much longer than expected. For example, importing all data from an old system. Running business rules during transform may cause the transform to take longer than expected, or cause the instance to slow down.īecomes an issue: When importing a very large amount of data. Review these performance issues to troubleshoot and improve the performance of your import set jobs. See the original article on the ServiceNow doc site: ServiceNow: Troubleshoot import set performance. Where I will record the values and their user ID for reference.This article is based on the ServiceNow documentation article. I am using this to create a database where users can make suggestions as to what a fields value should be… so the user could click on RecNbr 1 and see the values that are live but enter their own values into the STAGING table. Is there a way to get scriptcase to load the details even though there is no record in the staging table yet?Įxample table structure. Scriptcase will not load the Detail grids unless a record exists in the staging table for that RecNum. I have Detail Grids in the “Master/Detail” section of Scriptcase that use a variable I pass to this form in order to display the current data for the matching record from the live table. This empty table is a duplicate in structure to a live table that has data in it. I have a form that is pointed to an empty table, Im calling it my “Staging Table”.
0 Comments
Leave a Reply. |