Thanks for contacting Yellowfin. We don't have any documentation on using null or empty values for reference codes, so therefore I imagine it's unlikely they are supported. You could try putting in two inverted commas, like '' to represent an empty string, but that may not work in the way you hope. I notice that if you import a CSV with reference codes that contains with an empty value, Yellowfin does not process that row and skips over it.
Can I ask why you'd like to use them?
Kind regards,
Chris
Hi Maria,
Thanks for contacting Yellowfin. We don't have any documentation on using null or empty values for reference codes, so therefore I imagine it's unlikely they are supported. You could try putting in two inverted commas, like '' to represent an empty string, but that may not work in the way you hope. I notice that if you import a CSV with reference codes that contains with an empty value, Yellowfin does not process that row and skips over it.
Yes it does look like we only have the method of adding them with the calculated field workaround. I could create a new enhancement post for this if you like, however the general feeling around null values is that they are Bad News and should be avoided where possible.
There are wildcard values for reference codes, represented by a %, if that would prove useful?
Kind regards,
Chris
Hi Maria,
Yes it does look like we only have the method of adding them with the calculated field workaround. I could create a new enhancement post for this if you like, however the general feeling around null values is that they are Bad News and should be avoided where possible.
There are wildcard values for reference codes, represented by a %, if that would prove useful?
Hi Maria,
Thanks for contacting Yellowfin. We don't have any documentation on using null or empty values for reference codes, so therefore I imagine it's unlikely they are supported. You could try putting in two inverted commas, like '' to represent an empty string, but that may not work in the way you hope. I notice that if you import a CSV with reference codes that contains with an empty value, Yellowfin does not process that row and skips over it.
Can I ask why you'd like to use them?
Kind regards,
Chris
Hi Maria,
Thanks for contacting Yellowfin. We don't have any documentation on using null or empty values for reference codes, so therefore I imagine it's unlikely they are supported. You could try putting in two inverted commas, like '' to represent an empty string, but that may not work in the way you hope. I notice that if you import a CSV with reference codes that contains with an empty value, Yellowfin does not process that row and skips over it.
Can I ask why you'd like to use them?
Kind regards,
Chris
I would like to map them as 'Unknown' and skip the process of using a calculated field to do this
I would like to map them as 'Unknown' and skip the process of using a calculated field to do this
Hi Maria,
Yes it does look like we only have the method of adding them with the calculated field workaround. I could create a new enhancement post for this if you like, however the general feeling around null values is that they are Bad News and should be avoided where possible.
There are wildcard values for reference codes, represented by a %, if that would prove useful?
Kind regards,
Chris
Hi Maria,
Yes it does look like we only have the method of adding them with the calculated field workaround. I could create a new enhancement post for this if you like, however the general feeling around null values is that they are Bad News and should be avoided where possible.
There are wildcard values for reference codes, represented by a %, if that would prove useful?
Kind regards,
Chris
Hi Maria,
Hope you're having a good week.
Just wanted to check-in and see how it's all going. Was there anything you were needing from me to help get this resolved?
Another thought regarding the nulls, you could create a calculated field that converts the nulls to another value and then reference that instead.
Kind regards,
Chris
Hi Maria,
Hope you're having a good week.
Just wanted to check-in and see how it's all going. Was there anything you were needing from me to help get this resolved?
Another thought regarding the nulls, you could create a calculated field that converts the nulls to another value and then reference that instead.
Kind regards,
Chris
Hi Chris,
Yes, I wanted to skip the calculated field, but seems like the best option at the moment.
Thank you for following this up.
Hi Chris,
Yes, I wanted to skip the calculated field, but seems like the best option at the moment.
Thank you for following this up.
Hi Maria,
No worries. I'll mark this as complete if you're happy with the provided solution.
Kind regards,
Chris
Hi Maria,
No worries. I'll mark this as complete if you're happy with the provided solution.
Kind regards,
Chris
Yes, that is ok.
Thank you Chris.
Yes, that is ok.
Thank you Chris.
Replies have been locked on this page!