Autopopulate to become null on cancel

RE: Autopopulate to become null on cancel

vineethk0001 — Wed, 10 Apr 2019 17:24:22 GMT

Thanks Vivek

RE: Autopopulate to become null on cancel

viveku3486 — Wed, 10 Apr 2019 15:42:08 GMT

Hello Vineeth,

Give this code a try, It will work for you

a!pickerFieldUsers(
label: "Requestor",
labelPosition: "JUSTIFIED",
maxSelections: 1,
value: local!Applicant,
saveinto: {
local!Applicant,
a!save(ri!Request_Inputs.Requestor,local!Applicant)
},
required: true,
validations: {}
)
)

RE: Autopopulate to become null on cancel

vineethk0001 — Mon, 08 Apr 2019 09:51:57 GMT

sure, thanks a lot, will give this a try

RE: Autopopulate to become null on cancel

Stewart Burchell — Mon, 08 Apr 2019 09:50:29 GMT

Ok. Assuming your form is being loaded in a User Input Task in a Process you can set the default value of the User being captured in the Task Activity Class variable (set to fn!loggedInUser()) so that your rule input has this value when the form is loaded. You can then let the User delete it and then select any other User they are allowed to select, saving the value to the same rule input.

RE: Autopopulate to become null on cancel

vineethk0001 — Mon, 08 Apr 2019 09:41:18 GMT

Hi Stewart, my requirement is , on form load the "PickerFieldUser" will be populated with Default user(Logged in user), say "User1" will be populated, now the user who is filling the form can keep this "User1" or delete it and add "User2".

now whats happening is , on form load am able to populate "PickerFiledUser" with Defalut User(Logged in user),

but if the user wants to change this value and try to remove the default value to put "User2" into the field, its not leaving to do so, since as soon as i remove the defalut user, an event occurs by default (UNFOCUS or Keypress) which will again populate the "User1" into the field, not leaving me to key in "User2",

hope i was able to explain it properly

Thanks in advance

RE: Autopopulate to become null on cancel

Stewart Burchell — Fri, 05 Apr 2019 11:28:24 GMT

Ok, so I am confused. My original solution DOES satisfy your requirements. I tested it. So I don't understand why you then said:

[quote userid="34007" url="~/discussions/f/user-interface/14653/autopopulate-to-become-null-on-cancel/65660"]this i tried Stewart , but its not working, as this field will be editable and user can remove the value present and add new value.[/quote]

...as this indicates that this is NOT what you wanted...please help me to understand what it is you want as it's not at all clear now.

RE: Autopopulate to become null on cancel

vineethk0001 — Fri, 05 Apr 2019 11:13:18 GMT

No No, i want to have default value, if the user wants he can remove this default value and add his own value,

RE: Autopopulate to become null on cancel

Stewart Burchell — Fri, 05 Apr 2019 11:10:33 GMT

[quote userid="34007" url="~/discussions/f/user-interface/14653/autopopulate-to-become-null-on-cancel"]i have a PickerFieldUser, which am auto-populating, but the user can cancel the auto-populated value and key in other entry,[/quote]

That's what you said you wanted to do! Do you mean you want a default value added and that the User can only ADD to this value and only remove the values they have added but NOT remove the default User value?

RE: Autopopulate to become null on cancel

vineethk0001 — Fri, 05 Apr 2019 10:55:38 GMT

this i tried Stewart , but its not working, as this field will be editable and user can remove the value present and add new value.

RE: Autopopulate to become null on cancel

vineethk0001 — Fri, 05 Apr 2019 10:54:39 GMT

Hi Prateek, sorry , its not working, it gives an error as null value cannot be passed , when i cancel the autopopulated user

RE: Autopopulate to become null on cancel

PRATEEK BHATTI — Fri, 05 Apr 2019 10:28:13 GMT

Give below code a try..as it works for me.

a!pickerFieldUsers(
label: "Requestor",
labelPosition: "JUSTIFIED",
maxSelections: 1,
placeholder:"--Select a user--",
value: if(isnull(ri!Request_Inputs.Requestor),local!Applicant,ri!Request_Inputs.Requestor),
saveinto:{ri!Request_Inputs.Requestor,
a!save(local!Applicant,null)},
required: true,
validations: {}
)

RE: Autopopulate to become null on cancel

Stewart Burchell — Fri, 05 Apr 2019 10:20:56 GMT

Hi - I think you're over-thinking this. If the default value is being supplied in the value of ri!Request_Inputs then your code should simply be this:

a!pickerFieldUsers(
label: "Requestor",
labelPosition: "JUSTIFIED",
maxSelections: 1,
value: ri!Request_Inputs.Requestor,
saveinto: {
ri!Request_Inputs.Requestor
},
required: true,
validations: {}
)

RE: Autopopulate to become null on cancel

vineethk0001 — Fri, 05 Apr 2019 09:41:51 GMT

thanks for the reply Prateek , sorry but it dosen't work , as soon as i delete the autopopulated name , it comes back

RE: Autopopulate to become null on cancel

PRATEEK BHATTI — Fri, 05 Apr 2019 06:48:17 GMT

Hi vineethk0001,

Use "placeholder" attribute to keep the user picker empty until user enter some other user.

a!pickerFieldUsers(
label: "Requestor",
labelPosition: "JUSTIFIED",
maxSelections: 1,

placeholder:"--Select a user--",
value: local!Applicant,
saveinto: a!save(ri!Request_Inputs.Requestor,local!Applicant),
required: true,
validations: {}
)

Hope it helps!!