+5hi,
During the Creation steps in Deployment, I’ve had some problems because I used preserved SQL names (check, revoke) in the data model. How come the SF does not validate this during Creation? Or am I missing something?
The list of preserved words is getting bigger and bigger..
Best answer by Mark Jongeling
hi Mark,
Ah, I see the validation now, but it is only a warning (in testing I normally skip these warnings 😬 ). Shouldn’t this be an error as the sql code breaks when executing?
We did change the way the Software Factory handles these object names from 2022.1. When rolling out your model, object names are escaped using quotes ("”) around the name. This prevent an error from occurring and thus make it possible to roll out. We made this change due to Upcycled projects possibly having these object names. So the Warning severity is correct in this case.
I suppose you are working on the 2021.3 version which did not have these changes yet, then the severity may not be entirely correct. Many reserved keywords can be used in object names but indeed some are problematic.
+23Hi Tejo,
The Software Factory does have a number of Validations that validate the data model to see if any reserved keywords are used.
The SQL keywords you mentioned are in the reserved keyword list:
Can you check if you received any validation messages about the usage of these names? And if not, what type of objects where using these keywords?
+5hi Mark,
Ah, I see the validation now, but it is only a warning (in testing I normally skip these warnings 😬 ). Shouldn’t this be an error as the sql code breaks when executing?
+23hi Mark,
Ah, I see the validation now, but it is only a warning (in testing I normally skip these warnings 😬 ). Shouldn’t this be an error as the sql code breaks when executing?
We did change the way the Software Factory handles these object names from 2022.1. When rolling out your model, object names are escaped using quotes ("”) around the name. This prevent an error from occurring and thus make it possible to roll out. We made this change due to Upcycled projects possibly having these object names. So the Warning severity is correct in this case.
I suppose you are working on the 2021.3 version which did not have these changes yet, then the severity may not be entirely correct. Many reserved keywords can be used in object names but indeed some are problematic.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
