Ask the local knowledge assistant
NSIPA knowledge library
Task guidance for each service and workflow stage. Local guides describe NSIPA; upstream references may describe other releases. Your account determines available actions.
531 published entries across 18 services · 64 source-linked guides
2 matching entries · Page 1 of 1
Fetch and validate a connected CSV · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Retrieve the latest CSV from the selected connection and validate it using the saved source mapping.
What to do
- Choose the connected Data source and check Expected columns.
- Select Fetch and validate. A new fetch opens a draft with the source and mapping version. After a lost response, use the same Registry login and source from either browser to reopen the saved batch. Both browsers can reopen the same batch if they retry together.
- Open Reconcile records. Compare source and mapped values, then save any corrections or exclusions before sending for approval.
What you need
The connection must be configured and active. The CSV can contain up to 2 MB, 1,000 data rows and 40 columns.
Next step
Use the same draft through approval and the Data Bridge transfer. If it is returned, correct that batch and send it for approval again.
Common issues
For a sandbox test, select Synthetic connected CSV test only. Its headers are Reference and Test note. The fixture includes two versions of the same reference to exercise duplicate validation.
Published version 5 · public guidanceOpen this guide · Download plain text
Was this guide helpful?
Resolve a connected CSV fetch error · Master Beneficiary Registry · all
NSIPA local workflow
Provisional guidance
Recover when the connection is unavailable or Data Imports cannot read the response.
What to do
- Note the selected source, error and time. Use the same Registry login and select the same source under New import. Use Fetch and validate to reopen a saved batch whose response was lost. This works from another browser, including when both browsers retry together. If the workspace asks you to choose a match, open Transfers. Select Refresh history and use the batch reference because connected batches can share a filename.
- When the batch is reopened, continue from its current status. Use Fetch a new CSV only when you intend to start a separate import from that source. Repeat that action from the same earlier batch to find its separate import. To resume the original, open it by reference in Transfers.
- If the fetch never saved a batch, use the same action again once the source is available. Ask the integration administrator to verify the endpoint, credentials and CSV response if the error persists.
What you need
The endpoint requires HTTPS and a CSV response. Integration administrators check any server-side access credential.
Next step
Continue from the existing batch’s current status. Review a draft in Reconcile records. For a batch already sent to the Registry, check or refresh its receipt in Transfers.
Published version 9 · public guidanceOpen this guide · Download plain text
Was this guide helpful?