Issue above is a result of a known bug in 22R1. We are working to apply the latest Service updates and test again.
The issue I am having appears to be fixed in 22.1.4.Eric thank you the details. That was key in finding the solution. Mike
Eric, Thanks for testing. I tried again comparing your setup but still get the error. The only thing I see different is date localization. This is what I get if select “Validate” after Loading the data If I clear the CreationDate values it will validate. If I change a date to text by adding a leading ‘ (eg. ‘7/19/2022) It the row is identified as having a bad date. If I delete all data for date fields it will execute and validate changes in other columns.
We have worked through all of the items above but are now stuck on the issue that the Add-in won’t recognize “Date” columns. You can load the data directly from the table, run validate, and it returns an data type error. (Example Customer Info Creation Date. )
We have identified the two issues SE_Unauthorized → Solution: After creating a migration job a new projection is created for it. Admin must grant the project to the user executing the job, even if its the same person that created the job. ORA-20110: IC_FIN_Account_Tab.InsertError → Excel Date issue Issue still not resolved. If the Excel file has any date fields in will fail with this error, ex. CreationDate. We tried to hide the Creation Date from the job, which will allow you you to load/validate but fails on Insert I can leave the field in but delete all values before I hit validate/execute and it will run without error Has anyone see this issue before? Is there a format it must be converted too? I have a crud workaround for Creation Date but it doesn’t address the situation when I do need to update/insert a date value.
We are not sure why but somehow the account (IFSAdmin) lost permissions to the underlying view. After working through that we ran into the next issues which was ORA-20110: IC_FIN_Account_Tab.InsertError:… Literal does not match format string. This is odd since its validating the data in the spreadsheet that just came from IFS via the “Load” button. This has happened on both tables we tried to load. If feels like something is out of sync in our environments setup. (Note: this is a brand new implementation)
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.