Creating and setting value for custom profile fields

iftomkins - We are already doing this in our community where we store the required details of the user in the custom field rather than the cookie.

Regarding the custom field, at the moment this can be added via Li Professional services only, and that is at no additional cost, we have got many custom fields for our communities. They will set it up on your staging instance for review and then once you confirm, will be pushed live in your maintenance window.

Your custom field will be visible in the user profile data in the API response and will also be available in the metrics reports.

This is how you can access the Custom fields:

https://community.xyz.com/restapi/vc/users/id/[ID]/profiles/name/CUSTOM_FIELD

This is how you can set the value in the custom fields:

https://community.xyz.com/restapi/vc/users/id/[ID]/profiles/name/CUSTOM_FIELD/set?value=VALUE_TO_BE_SET

This works really well and would suit your scenario of showing the form only once to the user.

Hi VarunGrazitti ,

just to clarify a few points regarding the subject.

Regarding the custom field, at the moment this can be added via Li Professional services only,

--- if there is no on-going projects with PS, Support could be happy to assist you in this subject.

and that is at no additional cost

--- it is really case by case basis. In general, one-time setup and zero customization would be at no cost or low cost.

They will set it up on your staging instance for review and then once you confirm, will be pushed live in your maintenance window.

-- when the fields are added to stage server only, not production server, the studio publish will be disabled. most of the time, we will add to both stage and production at the same time.

<the custom profile fields> “will also be available in the metrics reports.”

--- it is not OOTB or by default, you need to explicitly tell Lithium that you want to include those fields in your user report.

iftomkins  I don't think you need custom content. You can manage it by  "Page Hitbox Content " area at skin's header section.

 Using JS.

VarunGrazitti  I was just giving him idea if this way it help him.

Thank you VarunGrazitti and bhupen ! I've made progress, but would love your advice, as I'm a bit stuck.

Lithium set up the fields, which is awesome. I'm now trying to set and retrieve values from the two custom profile fields:

profile.ideas_terms_accepted – Which is a checkbox
profile.ideas_terms_accepted_date - Which is date/time, and the value must be a signed decimal integer. It is interpreted as milliseconds since Jan 1, 1970. The value by default is displayed to include time.

So far, this is my code to set and retrieve the value for profile.ideas_terms_accepted field:

<#assign response = restadmin("/users/id/${user.id}/profiles/name/ideas_terms_accepted/set?value=true")/>
<#assign terms_accepted = rest("/users/id/${user.id}/profiles/name/profile.ideas_terms_accepted").value>
alert('${user.id}');
alert('${terms_accepted}');

It's not working. The ${user.id} is returning properly, but ${terms_accepted} is not returning a value. I tried both "true" and "checked" for the field value.

For the profile.ideas_terms_accepted_date field, I'm not sure how to generate a "signed decimal integer". I searched the community for that phrase and nothing came up.

Tips on settings and getting these values would be awesome!

- Alan

bhupen I appreciate your suggestion. I would prefer to do this via JS and cookies, but our Legal team would prefer this value be stored in a custom field value. :/

hi iftomkins 

not too sure about the exact context

but one thing noticed was your first REST call  URL:

.../profiles/name/ideas_terms_accepted/...

and your 2nd REST call to retrieve URL was this:

.../profiles/name/profile.ideas_terms_accepted/...

 should it be just .../profiles/ideas_terms_accepted/... (without the "profile.") in the 2nd REST call?

Thanks JasonL . The profile.field format I had copied from another rest API call in our code, not sure why it worked there but not here. What did end up working is a combination of 1) your suggestion for formatting the URL, and 2) changing the 2nd call from rest() to restadmin().

Here's the working code:

<#assign response = restadmin("/users/id/${user.id}/profiles/name/ideas_terms_accepted/set?value=unchecked")/>
<#assign terms_accepted = restadmin("/users/id/${user.id}/profiles/name/ideas_terms_accepted").value>
alert('${user.id}');
alert('${terms_accepted}');

Also, a note on checkbox fields, the values that work seem to be checked/unchecked, not true/false.