on 2022 Oct 11 9:11 PM
Hi experts,
I am using the package in PackageLink to achieve the next: Convert a property to ParentH1.
ID,EVDESCRIPTION,PROPERTY X, SCALING, PARENTH1
CUST_001, TEST_CUST1, TOT_CUST, SCALING, PARENTH1
CUST_002, TEST,CUST2, TOT_CUST <----------------- In this case TEST will end as one column and CUST2 will be a different column ending the value of CUST2 in the column SCALING. That generates an error in the step 4.
4. Importing Flat File (here I map Property X with PARENTH1 in the tranformation file to assing the property as PARENTH1.
I try to solve this bye doing the NEXT:
In the transformation file to export the data to file I have set the EVDESCRIPTION in the mapping section as
EVDESCRIPTION= *str()
This way the comma in the description will be blank and the description won´t be generating this error, right? however seems that the file is generated internally, takes the tranformation and the actual file is created, so, the text after the comma in the description generates in the actual file another column:
I.E.
Record:
ID,EVDESCRIPTION,PROPERTY X, SCALING, PARENTH1
CUST_001, TEST_CUST1, TOT_CUST, SCALING, PARENTH1
CUST_002, TEST,CUST2, TOT_CUST
CUST2 once more finish in the scaling column.
My question is: Is there any way to change the separator for the export file program to make it maybe TAB or ;??
I have try also with js:%external%.replace("," , ";") in a conversion file inside the Tranformation FILE to change it before exproting, it won´t work, beside change all the separators.
A work around that I was thinking is: Importing the Customers without text from the beggining, assing the hierarchy using flat file, then reimport the cusotmers to include the description from BW :).
Your thoughts are very WELCOME:
Thank you very much.
Best Regards. !!!
Request clarification before answering.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.