Replace Data Source with Import Set Api

[Meloper]

hi,

im aware of that function "System Web Services" but i want to keep the Data Source  

or at least the existing staging table (import set table) and the transform scripts.

I would like to rebuild existing data source logics due to the completion of a database.
This means that the teams should send the data to us using the import set api.
I would like to keep the data source as a “shell”.
This means that the import set tables, field scripts and transform scripts contained in it should remain.

However, I would like the data source not to fetch the data “itself” but for the team to send the data.

[jenny464din]

Hello, @Meloper 

1. Disable Data Source Fetching:

Locate the Data Source: In your ServiceNow instance, navigate to System Data Sources. Find the specific data source you want to modify.
Disable Fetching:
Open the data source record.
In the Data Source section, locate the Fetch Method.
Change the Fetch Method from its current value (e.g., "Scheduled") to "None".
Save the changes.
2. Preserve Existing Components:

Import Set Tables: These tables will remain as they are. They will be used to store the data imported via the Import Set API.
Field Scripts: Any existing field scripts associated with the import set table fields will continue to function as intended.
Transform Scripts: These scripts will also be preserved. They will be executed on the imported data to transform it into the desired format for your ServiceNow instance.
3. Enable Data Import via Import Set API:

Import Set API: Utilize the ServiceNow Import Set API to programmatically create and populate import set records.
You can use scripting (e.g., JavaScript, Python) to interact with the API and send data to the designated import set table.
Refer to the ServiceNow documentation for detailed information on the Import Set API and its usage.
4. Test and Monitor:

Thoroughly test the data import process using the Import Set API.
Implement monitoring mechanisms to track the success and failures of data imports.
Regularly review the imported data to ensure data quality and integrity.
Key Considerations:

Data Volume: If you anticipate high data volumes, optimize your import scripts for performance.
Error Handling: Implement robust error handling mechanisms to address potential issues during data import.
Security: Ensure proper security measures are in place to protect your import set tables and the data they contain.
By following these steps, you can effectively repurpose your existing data source as a "shell" while maintaining the critical components (import set tables, field scripts, transform scripts) and enabling data import through the ServiceNow Import Set API.

Best Regards

[Ankur Bawiskar]

@Meloper 

you can re-use the staging table which got created as part of that data source.

Give that table's endpoint using import set API to 3rd party and inform them to push the data.

what's the challenge?

Once they do your transform map and field map, transform scripts will run.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@Meloper 

Thank you for marking my response as helpful.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Meloper]

Hi Thanks for your Answer but this time it was "just" Helpful 🙂
But thanks anyway, of course, I appreciate your engagement