Friday 6 July 2018

Number of dimension values specified is different from the number setup in the active format for data entities

Lets discuss about the one of the issue (Number of dimension values specified in application development is different  from the number setup in the active format for data entities ) which anyone might face while import or export operations using entities.
Lets assume there is one of the common scenario in which you are uploading records for customer groups  along with its  financial dimensions using data entities.












Problem : Number of dimension values specified in application development is different  from the number setup in the active format for data entities.

Root cause :  There is difference in number setup of  excel file and active format of data entities.

Solution : Check your active format for financial dimension on following navigation (General ledger - Charts of accounts - Dimensions - Financial dimension configuration for integrating applications) and update excel file according to format or change its format. Then try to import data by using entity.

Below is the file format for customer groups uploading process through entities. For dimension value we are using  format Dimension1-Dimension2-Dimension3.


2 comments:

  1. Hello, say you have several integrations and each uses a different set of financial dimension. Since you can only have one dimension of each active at a time, what would be the solution so user doesn't have to go into GL>Dimensions configuration each time before uploading to activate the dimension? In my case, i'm using data entities to import General journal and atleast one of the integration will be setup as recurring job which is further making this difficult.

    ReplyDelete
    Replies
    1. Hi, you need to check it out whether you can skip out this dimension configuration validation or not. There is a class know as Dimension Resolver and it has a method namely "checkFormatCreated" check it. But make sure you should do skipping or anything just for you entity. Or try to unmark the check box available on entity mapping for validating field. For different set of financial dimension perform add some logic on entity or check it out where suitable.

      Delete

Note: only a member of this blog may post a comment.

Connect and upload in azure blob with azure key vault using x++

 Today, I will be sharing details about file upload in azure blob using azure vault that includes pre requisite and code snippet used to it....