Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello, i have a large document in tfileinputExcel that pass trough an tMap
in metadata all the fields are String with only two exceptions(prices)
This is my metadata, and when i run my job i got this stupid issue "For input string"
The Field "1 ano" is inside [Garantia_Balcao]
You can check this out in my xls file above
Anyone can help me in this issue?
Yes, UPC is the header i understand, but my error persists in my big Job, the error appears random form, i cant spread my full current Job
To Remind, my data parse correctly, but this console is annoying "For input for string" like 1 hundred times
I also uploaded my Sample Input in "Zip" with my current Test Job
I will try the Die on Error, but the data parse correctly, but this console still saying this annoying message
And the columns doesnt still the same in all sheets
But i have a Metadata for every Sheet, i think this isnt the problem
Hi @iansoares is it possible for you to post a copy of your file that causes this so that I can take a look at it? Please don't post it if it contains any personal or confidential data. If it does contain personal or confidential data, could you remove that data or create a version of the file that is safe to share, but still exhibits the same problem? I *think* I might know why this is happening, but I need to see the file to test my theory.
Forget the previous post, I see that you have already uploaded your data. I have tested it and the only way I get anything like the UPC error is if I do not filter out the header row. Once I do that, the data runs OK. My config looks like this....
Can you share a file which does exhibit the original problem. If the file you shared is supposed to exhibit the original problem, it didn't when I imported it through the metadata ---> File Excel import and used that metadata for the component's schema. Can you try that?
Did u enter the Schema?
Yes i sent you the file whose contains error
Sorry, you sent me that message while I was writing my last response. I will check it now 🙂