ServiceNow Remote Instance - Spoke

[Geoff_T]

I am trying to use the 'ServiceNow Remote Instance' spoke. When I choose the 'Update Remote Record' action to be added I get a warning pop up - 'A dynamic action error occurred.'

Then I am unable to choose a remote table from the drop down.

Anybody know what is causing this error?

Thanks

[Pradeep Sharma · Accepted solution]

Hi Geoff - This generally happens when the connection and credential is not setup properly. You can also look at flow execution to debug the issue.

[Geoff_T]

Hi, this could be the issue. I didn't realize I had to set up connection / credentials for this. I have no executions to review as I'm simply just trying to add it to a flow initially.

The use case I am considering this spoke for is updating lower environment tables from Production environment triggered off of a catalog item. Am I right in considering this spoke for this use case - before I delve into looking at the connection / credential set up?

Thanks

[Pradeep Sharma]

Two options here.

1. The ServiceNow Remote Instance spoke can be used if you have several distinct prod instances, for example one external facing with CSM and one for internal workflows. Data transfer will happen conditionally from within a flow. You can also use this spoke to escalate tasks to an external remote ServiceNow instance, for example one that belongs to a service provider who covers your third-party support for a sub-set of your tasks.

2. Instance data replication (IDR) copies data from a source instance to one or more target instances. It has high flexibility in managing what data is being replicated and under what circumstances. The transferred data can be transformed and mapped to other tables and table columns in the target instances. Business rules can trigger post-replication flows to generate notifications after completion of the transfer. IDR replicates data and not metadata, configurations nor most user and system tables. In contrast to integrating via IntegrationHub spokes (usually REST/SOAP), which are part of business workflows, IDR is not supposed to be transactional. It is purely a means to copy or synchronize data between a producer instance and one or more consumer instances.

On the security side, IDR has significant benefits as it runs on dedicated infrastructure that is integrated with ServiceNow, delivering security, redundancy and support across all data centers. Data that is in transit during the unlikely event of a crash is recoverable.

Examples: IDR is used to replicate data on an ongoing basis within a replication set of instances. The main use case would be to sync multiple prod instances, for example for large customers or to sync prod data to a UAT instance. Data transform allows modifications by mapping the data, for example localizing it during replication

Reference:

https://community.servicenow.com/community?id=community_article&sys_id=3dcee45cdbc31010f21f5583ca961...

- Pradeep Sharma

[Geoff_T]

Correct - needed to set up the connection and credential info.

https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/administer/integrationhub-store-spokes/task/setup-rem-instance.html#setup-rem-instance

Thanks