Learn about Redwood and be one of the first to join the conversation

Visit Redwood Community
Issue with Data Management pushing data across instances with alternate Period Hierarchy — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Issue with Data Management pushing data across instances with alternate Period Hierarchy

Received Response
1
Views
1
Comments

Hi

We currently have an issue when running across application integrations (two different PODs) using Data Exchange/Management.

The source application where we are running the integration from has an alternate hierarchy in the period dimension and we are pushing from an ASO cube.

When running an integration it fails to import it into data management the staging tables.

Initial error was an unknown member [Period].[Aug] (in the logs so failed to extract data in the MDX statement), I then used the period mapping tables to get around this by adding YearTotal].[Aug as the period, so we then got it to extract but got a non-numeric amount rejection (even though the integration was set to all data types) so think it wasn't picking up the correct column for the amount. Tried lots of other things and had several different rejection codes in the logs another was a blank row even though data was in it?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!