Issues with a!PickerFieldUsers() function

RE: Issues with a!PickerFieldUsers() function

viveku3486 — Thu, 22 Feb 2018 10:12:20 GMT

Hey Brad,

I checked and found that the value stored in database column is not null, Its a value "NULL" that is why its taking default username who corresponds to "NULL"

RE: Issues with a!PickerFieldUsers() function

bradc — Tue, 20 Feb 2018 14:35:36 GMT

Hi - I have not encountered this behavior on my side and have not been able to recreate it. Did you search for the user that is appearing in the Inactive user list as well? Can you also try putting typename(typeof(local!tempUserValue)) in your textfield component to see what type is being returned by this local variable? Perhaps that will shed some light on the issue.

RE: Issues with a!PickerFieldUsers() function

viveku3486 — Mon, 19 Feb 2018 13:03:15 GMT

Hey Brad,

I checked this by placing a textfield control and its shows the value null(Which is the expected outcome), Also I tried by removing with() clause but it haven't make any difference. One more thing i noticed is its taking the same user name as a default value and when I checked the directory there is no such user with that username.

RE: Issues with a!PickerFieldUsers() function

bradc — Fri, 16 Feb 2018 15:38:04 GMT

I am not sure why that is happening there. Is it a user name that has been selected in another instance of this rule? Perhaps the indexes are confused mixed up somehow? Have you tried adding a textfield to this expression to debug the incoming value of local!tempUserValue?

Also - you do not need the with() wrapped around the pickerField unless you intend to declare a local variable to be used in the pickerField. I doubt this is causing your issue, but it is not necessary.

RE: Issues with a!PickerFieldUsers() function

viveku3486 — Fri, 16 Feb 2018 14:41:29 GMT

Hey Brad,

I got the issue actually it was the incorrect variable name causing the issue. Now its allowing me to save the values, But i'm still seeing random username as a default value, Even the expected default value is null. Any idea why that is happening?

RE: Issues with a!PickerFieldUsers() function

bradc — Fri, 16 Feb 2018 14:15:19 GMT

The username you are cancelling out is attempting to save into index position 10 of ri!ContentMetricsUpdatedValue_cdt. I am assuming you are generating this rule for each item in ri!defDataContentMetrics_cdt, but the CDT you are saving to does not have the same length, so your ri!index of 10 is not present for ri!ContentMetricsUpdatedValue_cdt.

If you believe ri!ContentMetricsUpdatedValue_cdt does have the correct length, you should also check that ri!ContentMetricsUpdatedValue_cdt is marked as an array on your inputs.

RE: Issues with a!PickerFieldUsers() function

viveku3486 — Fri, 16 Feb 2018 13:50:03 GMT

The value returned in local!tempUserValue is not valid as the cdt which i'm getting from API call has null value for it but its showing some random user name. When I cancel out that username it shows the above error.

RE: Issues with a!PickerFieldUsers() function

viveku3486 — Fri, 16 Feb 2018 13:48:27 GMT

Attached is the error message I'm getting

RE: Issues with a!PickerFieldUsers() function

bradc — Fri, 16 Feb 2018 13:37:03 GMT

Hi - It may help if you were to provide the error you are receiving to properly diagnose. Are the values returned in local!tempUservalue valid Appian usernames?