Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
cancel
Showing results for 
Search instead for 
Did you mean: 
ubanerjee
Creator
Creator

SYS,GENERAL_EXCEPTION,Input string was not in a correct format during MARTS Validation

In our Environment we have a master project and several other projects where developers make changes. For one of these projects I imported the Entity and Mapping changes from the UI. Validate worked for the DW and DM. 

Next I exported the project CSVs and merged the DM changes from the Developer's project into the Master. There were changes to around 5 Facts and 6 Dimensions.  The import completed successfully using the CLI.

Upon running validate Compose throws the following error in Master. 

ubanerjee_0-1632332686625.png

How should we go about debugging this issue? In the past I have tried to restore a backup and tried to bring one Dimension or fact at a time. Is that the ideal way or is there a way to query the sqllite db or json file to identify the root cause of this issue? 

 

Labels (2)
1 Solution

Accepted Solutions
ubanerjee
Creator
Creator
Author

Hey @Nanda_Ravindra 

 

This issue is closed now. 

View solution in original post

3 Replies
Adam_Herman
Support
Support

Hi @ubanerjee ,

I can confirm that you've raised a case for this issue back then, although, as per the case details, I'm not sure if you have managed to resolve this.

If you still need any further assistance in regards, then kindly raise a new incident for the same, attaching the previous one, so we can continue with our investigation. 

Regards,

Adam

Nanda_Ravindra
Support
Support

Hello @ubanerjee,

        Let me know if you still seeing this issue, and I'll happy to re-open the case for you and work towards getting a solution for this issue.

 

Thanks,

Nanda

  

ubanerjee
Creator
Creator
Author

Hey @Nanda_Ravindra 

 

This issue is closed now.