- Do you have any recommendations (alert point) when using an identifier from a source system. In connection with this following documentation.
- Need/wish : Use of already existing codes as "reference" (from a reference base still used for some applications). We thus wish to apply codes already used and automatically apply new ones.
We are thinking of using the SemQL query method (to be defined - idea: search for the last code available in the list and "tag" it as "activated" once applied.)
Do you think is a good method / is possible ?
Thanks for your advice!
Best Answer
S
Subham Dixit
said
over 2 years ago
Hello Rlhostis,
Yes, you can use the Code attribute in the ID generation using the SemQL, but it won't apply to the existing records, it will be only applicable to the newer one that you will create and always take the value of 'code' attribute which you will provide while creating a record, as it's a Primary key so there's won't be 2 same code values exist otherwise it will throw an error.
Thank you.
1 Comment
S
Subham Dixit
said
over 2 years ago
Answer
Hello Rlhostis,
Yes, you can use the Code attribute in the ID generation using the SemQL, but it won't apply to the existing records, it will be only applicable to the newer one that you will create and always take the value of 'code' attribute which you will provide while creating a record, as it's a Primary key so there's won't be 2 same code values exist otherwise it will throw an error.
Régis L'HOSTIS
- Do you have any recommendations (alert point) when using an identifier from a source system. In connection with this following documentation.
- Need/wish : Use of already existing codes as "reference" (from a reference base still used for some applications). We thus wish to apply codes already used and automatically apply new ones.
We are thinking of using the SemQL query method (to be defined - idea: search for the last code available in the list and "tag" it as "activated" once applied.)
Do you think is a good method / is possible ?
Thanks for your advice!
Hello Rlhostis,
Yes, you can use the Code attribute in the ID generation using the SemQL, but it won't apply to the existing records, it will be only applicable to the newer one that you will create and always take the value of 'code' attribute which you will provide while creating a record, as it's a Primary key so there's won't be 2 same code values exist otherwise it will throw an error.
Thank you.
Subham Dixit
Hello Rlhostis,
Yes, you can use the Code attribute in the ID generation using the SemQL, but it won't apply to the existing records, it will be only applicable to the newer one that you will create and always take the value of 'code' attribute which you will provide while creating a record, as it's a Primary key so there's won't be 2 same code values exist otherwise it will throw an error.
Thank you.
1 person likes this
-
LOV label in Named Query
-
How we can set Dynamically changing Form field Description?
-
Is it possible to have a conditional survivorship rule based on a SemQL filter (akin to the filter on privileges)?
-
Where Do I View 2 Merged Records?
-
Show/hide an attribute in a form
-
Restrict access of attributes
-
Is it possible to manage visible/invisible value in List depend on user role??
-
Why am I unable to merge duplicates?
-
How are child records selected when parent records are manually merged?
-
Can the response from the API Call Response can be formatted differently in the JSON output?
See all 178 topics