Data Feed Specifications & FAQ

Click the link below for the most current Data Feed Specifications in Excel format.

Emburse Enterprise Data Feeds Specs.xls

For FAQs based on your role, see Quick-Start Guide to Data Feeds.

What is the address/hostname for the file server?

Because Emburse Enterprise has multiple FTP addresses, your Emburse Enterprise CSM will provide you with the FTP addresses assigned to your organization for Production and, if applicable, QA/UAT.

Alternatively, using the tables below, you may look up the FTP address based on the URL in your browser's address bar when you are inside the Emburse Enterprise app.

Production FTP Addresses

If your URL is....	Your FTP address is...
https://app.chromeriver.com	ftp.chromeriver.com
https://app.eu1.chromeriver.com	ftp.eu1.chromeriver.com
https://app.ca1.chromeriver.com	ftp.ca1.chromeriver.com
https://app.us2.chromeriver.com	ftp.us2.chromeriver.com

QA/UAT FTP Addresses

If your URL is....	Your FTP address is...
https://app.chromeriver.com	ftp.chromeriver.com
https://app.eu1.chromeriver.com	qa-ftp.eu1.chromeriver.com
https://app.ca1.chromeriver.com	qa-ftp.ca1.chromeriver.com
https://app.us2.chromeriver.com	qa-ftp.us2.chromeriver.com/

Where can I find Feed Issues files?

The issues file will be attached to the Feed confirmation email.

Some issues files are available on the FTP site in the /files/FeedIssues directory.

Why am I not receiving Feed Confirmation emails?

You must be subscribed to the email notification for each feed via the Notifications admin screen.

Be sure you are subscribed to email notifications for each data feed in both the Prod and QA/UAT environments so that you will know if one fails. 

Often when the user who was originally configured to receive these emails departs an organization, no replacement user is added. An admin with appropriate permissions can add you and/or other users to the subscriber list via the Notifications admin screen.

Why did my new data feed fail the first time I loaded it?

The first time you load a new data feed into the system, it may fail because it surpasses the number of changes allowed. You may easily reprocess the feed following the directions under Reprocess Failed Data Feed in the Data Feeds Admin Screen article.

I changed the case of a word in a data field and re-ran the data feed. Why isn't it appearing correctly now?

Unlike changing the length or value of data, simply changing a letter from uppercase to lowercase (or vice versa) will not trigger an update in the database when the feed runs again. To trigger the change, you must also change data length or data value in one of the fields, run the feed, undo the length/value change (but keep the case change) and then run the feed again.

For example, if you wanted to capitalize the surname "Smith" in the Person Data feed, you could:

1. Change "smith" to "Smithe."

2. Run the Person data feed.

3. Change "Smithe" to "Smith."

4. Re-run the Person data feed.

Why isn't the Person record being updated by the Person feed?

Be sure that person record isn't in an issues file.

Be sure the person record is not locked. If the People Admin Screen has the 'Locked (no feed updates)' checkbox checked, you will need to uncheck it.

You cannot change a user's Unique ID by updating it in the Person data feed file—it must be updated via the People Admin Screen. If the Unique ID is changed only via the Person data feed, the system will attempt to create a new person record and it will fail. You will see this in the issues file.