Epic SER Aggregation Issue

:bangbang: Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.

We are configuring the Epic SER connector in SailPoint. The test connection to the SFTP location is successful, and SailPoint is able to locate and access the SER extract file. However, during aggregation, no accounts are being pulled in from the file.

The extract file (.csv) meets the connector requirements:

  • Delimited file with a header row

  • No Byte Order Mark (verified using UTF-8 encoding)

  • Data rows match header length

  • Contains an ID column and other required fields (e.g., Provider name, Clinician/Title, Ref source type, etc.)

We have also validated that the same file works when tested with a Delimited File connector, so the format and data are valid.

Attribute Mapping

Schema

csv header:

image

What additional configuration or mapping is required for the Epic SER connector to successfully read and aggregate records from the extract file?

Did you also set the follow up?

{5BBF373D-075E-47BF-A674-EBFDB4669410}

I would also validate that you have the correct delimitator for the file. Easy way to figure this out is to open the csv file notepad or any text editor.

Hi Aishwarya,

Please go through the below provided steps to troubleshoot the issue.

  1. Open the csv file in notepad++ to check if you see any data issue.

  2. Ensure your file contains all the mandatory attributes defined in the IDN source schema, such as a unique identifier (ID) and other required fields.

  3. Check that the schema attribute names in IDN perfectly match the column headers in your Epic SER file. Any discrepancy can cause a complete aggregation failure.

  4. Check for the logs provide the most detailed information about why an aggregation failed.

–> Look at the most recent aggregation task in the “Aggregation Activity Log.” If the log shows “No accounts pulled in” or no errors, I would strongly suggest problem with the file’s content or formatting, as the connector is technically functional but can’t interpret the data.

At last also try to check the source logs in VA under ccg folder.

Do let me know if in case that works

IHTH :slightly_smiling_face:

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.