- SS&C Blue Prism Community
- Get Creative
- Product Ideas
- BI Data not mapped with Large API Calls
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
We have a process that uses the AWD REST API to index a large amount of data that is scraped from a PDF by a bot. We have found that this large post of Indexing often results in data not being successfully mapped to BI. After speaking with Customer Care, there is no obvious reason why the Mapper doesn't capture all indexing. This missing data causes confusion with downstream reporting as the CSD has the data but the report does not. The only way to correct the mapping is to delete the indexed value and index it with the same data moments later which can result in the in reps spending a significant amount of time manually correcting the data so the reporting is correct.
It would be nice if there was a nightly batch cycle that could reconcile the BI LOB tables against the AWD Indexing to ensure the BI tables contain the correct most recent indexing, as clients do not have access to the Live LOB Data and not all fields that are configured for BI are mapped to the AWDBE table for clients to build a custom solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- New 830
- Duplicate 76
- Needs More Info 51
- Reviewed 214
- Under Consideration 151
- Not Planned 83
- Planned 54
- Planned-Later 21
- Planned-Next 6
- Planned-Now 11
- Delivered 136
