and more in a single search tool across platforms. Read the announcement here. |
06/22/2023 07:18 AM
We have configured a few dynamic attributes. One should select the Organization (customer column). We have a few issues with that. Tried multiple things with single select from SQL query and user column customer.
Imagine two organizations. A with key 1 and B with key 2.
Query: select customername as id from customer
Works fine on create user. We select A and it is set. But if we change the value in update user to B, it behaves strangely. In the approval we see that a change is made from old value A to new value 2. If we approve it, the customer column on user is set empty.
Query: select customerkey as id, customername as inlinedescription from customer
Leads to very strange behaviour in child dynamic attributes. If we refer to the value of parent attribute, it still seems to contain the name and not the key.
Query: select customerkey as id from customer
Doesn't really work for end user because it's just technical keys.
It seems like there is some implicit processing on this column I couldn't find any documentation on.
What is the right way to select customer via dynamic attribute?
06/25/2023 10:18 PM
Thanks for your patience, we are looking into this and we will keep you posted on this.
07/10/2023 06:43 AM
Hi,
We are also facing the same issue, we are creating the user record with the customer data as @ASA pointed, it was removing customer attribute from user table without setting the new one)
but the pain is that, trying both ways the issue remains same, the user table is not getting updated with the updated organization data passed from "user update form".
SQL for Organization(Customer) dynamic attribute: select c.customername as ID from customer c where c.customername = SUBSTRING(${organizationname},1,LOCATE(":", ${organizationname})-1)
It works fine and inserts the relevant customerkey in the user table record, when we update the parent attribute it doesn't update the customer attribute and old organization remains there (Please note: when earlier we were using customerkey as id, the same update operation was behaving as
07/10/2023 06:47 AM
Hi,
by now we opened a ticket for this and it's allready in engineering. Might be a bug, I'll keep you posted 🙂
07/11/2023 05:28 AM
Thanks for the update @ASA