+2I am deploying a project to Snowflake.
On a table I get the following error:
Object reference not set to an instance of an object.
As read in another ticket I did a ‘Save and reload' but unfortunately that did not solve the issue.
It;s on deploying the data cleansing script however it does not show me the script in the deployment log, I only see the error message. Is there an easy way i can see what lookup column is causing the issue ?
Best answer by Roy V
Apparently the issue was that the generated scipt caused an error
when it involves
This has been sent to the product team and is waiting to be solved and released.
This can then be found in the release notes.
+5Hi
Is there any way you can be more specific about what you do to get this error?
For example you say it happens on deploying a table. There is some steps that will be deployed, what part fails.
Is it only this table that fails and if not what are the differences with those that work and those that do not.
+2Hi Thomas, here some more details:
It is when deploying a table, where the error occurs on deploying the data cleansing rules.
As you can see you can click on the error but not on a/the script being used so I do not know where to look to find the cause of the error.
Other tables do not have this issue but there are not many strange things happening, just 8 lookups and normal copy columns from the mapping.
The error details:
Any suggestions/ideas?
+5Hi
Can you please try deploying all objects associated with the table? To do this, right-click and select Deploy and then select Review task and then make sure all deployment steps are checked, and click Start. Do you still get the error?
If the error persists, please send screenshots of the table with its mappings and all the fields (including any transformations on fields) and screenshots of the table settings
+2Hi Christian
The error remains after processing al the related objects. I also checked if all the valid tables were created where lookup fields to exist. Columns with no mapping I also did a test with to set them to 1 but that didn’t solve the issue.
Table settings are all default and data extraction is full load, no history.
Transformations:
+2I removed all lookup fields and then I can deploy the table again.
I will just manually add them again and see if the errors pops up again.
I also have to remap the fields so all of this is quite time consuming. If the error would tell what the object reference is that is missing then it would save a huge amount of time.
+2The issue is with the fixed value in join columns in combination with snowflake.
TimeXtender adds quotes around is but this causes the error.
See below where I just added the CountyID = 10.
Can you pick this up with the development team?
+5Can you please confirm the data type of the COUNTYID field?
I am able to both add a join with a fixed value for a varchar field, as well as a number field, in a Prepare instance with Snowflake storage
+2that’s strange. When I add a join on either an integer field or on a varchar field, they both give the warning mentioned. The fiield below is an integer field.
It’s not the quotes causing the error but adding a fixed value (where the field does not matter)
+2I have more tables now with the same issue.
I can deploy wthout the join on the fixed value but when I add the necessary fixed join it runs into the error.
I don’t know where it is related to, I can add it to another table and there it works fine.
Maybe have a call to inspect together?
+2Maybe it is good to mark this issue as unsolved, that’s something I can not do.
+2Apparently the issue was that the generated scipt caused an error
when it involves
This has been sent to the product team and is waiting to be solved and released.
This can then be found in the release notes.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
