I am trying to use the action "Data: add a new row to another table using values from this row" but when the data gets added to the other table, the value of the column that should be Yes or No changes to TRUE or FALSE. The original column is an Enum that requires Yes or No. I have tried to figure out a workaround without luck.
Any advice? Thanks.
Solved! Go to Solution.
@mdanaher31 wrote:
but when the data gets added to the other table, the value of the column that should be Yes or No changes to TRUE or FALSE.
Could you mention what is the base type of the enum column or more importantly the other table's column where it is updating through action.
My testing did not show any problem in saving in backend as well as showing up in the email delivered from automation, properly as Yes/No Values.
Email received from automation:
Backend data saved:
Column configuration:
The column saved in another table through action:
In the other table also the column type is "enum" with "Yes", "No" enum options.
May we know any specific reason, you would like it to be 'Yes" and "No" even in the backend. For Y/N type of column the expressions , the backend stores TRUE or FALSE and further expressions can be built with those TRUE/FALSE values.
Based on your response, we could suggest a better option/workaround.
Hi! Yes, our IT team has built an Okta integration that is triggered only by Yes/No and not by TRUE/FALSE. I was asked not to disrupt this integration. I tried creating a virtual column that uses the IFS() function to change TRUE to Yes and FALSE to No but this is also not working.
You could change the column type to Enum with two possible values: Yes/No, instead of a Y/N type column.
Hi! That's the weird part. It is an Enum column with the possible values of Yes and No.
@mdanaher31 wrote:
but when the data gets added to the other table, the value of the column that should be Yes or No changes to TRUE or FALSE.
Could you mention what is the base type of the enum column or more importantly the other table's column where it is updating through action.
My testing did not show any problem in saving in backend as well as showing up in the email delivered from automation, properly as Yes/No Values.
Email received from automation:
Backend data saved:
Column configuration:
The column saved in another table through action:
In the other table also the column type is "enum" with "Yes", "No" enum options.
As @Suvrutt_Gurjar suggested. Please check the Base Type of the Enum column and make sure it is set to Text.
Hi @Joseph_Seddik ,
Nice to see you back in the community.
@Suvrutt_Gurjar I'm glad to hear from you again my friend ๐
User | Count |
---|---|
17 | |
14 | |
10 | |
7 | |
4 |