Conditional profile fields don't appear in the backend
By Marc on Tuesday, 15 January 2019
Posted in General Issues
Likes 0
Views 251
Votes 0
When we make a profile custom field display based on a "conditional" gender selection, we are able to make different profile fields appear for ladies and gents based on the gender selected.
However, as soon as we make the field conditional, its no longer visible in the back-end administration system.

Is there any way we can make all fields visible in the back end, but conditional in the front-end.
Without this, user support becomes difficult as we cannot see all the profile details.
Hi there,

It is not possible to achieve this currently. Those settings will be reflected on both backend and frontend and only can be viewed on that particular workflow only.
Abdul Warith Norudin
·
Wednesday, 16 January 2019 10:22
·
0 Likes
·
0 Votes
·
0 Comments
·
Okay....so if set fields on a profile to appear conditional on a specific gender selection, when viewing user profiles from the backend I cannot view those conditional fields at all?
Marc
·
Thursday, 17 January 2019 20:16
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

Yes that how it should behave currently. You cannot view those conditional filed as they need to be fulfilled first in order for them to show and it is applied to both frontend and backend.

Right now, you only can see them on workflow here http://take.ms/W0qTj or when those conditions a fulfilled only(for backend and frontend).

Thanks for your understanding.
Abdul Warith Norudin
·
Friday, 18 January 2019 11:24
·
0 Likes
·
0 Votes
·
0 Comments
·
.... or when those conditions a fulfilled only(for backend and frontend).


This statement is not quite true.
The conditional fields work fine and display correctly from the front end.
I can also see the conditional fields from the backend workflow.
However, I cant see the fields when using the user view from the backend, irrespective of whether the conditional rule has been met or not. (see attached)
Marc
·
Friday, 18 January 2019 13:43
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

After further check it seems that there are issues on our end where those conditions are check wrongly. Logged this issues internally and will included on our ES v3.0.

Thanks for your understanding.
Abdul Warith Norudin
·
Friday, 18 January 2019 15:21
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you!
Marc
·
Friday, 18 January 2019 21:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi there,

You are most welcome.

Just for your information, I have locked and marked this thread as resolved to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding.
Irwin
·
Friday, 18 January 2019 21:52
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post