Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Form Capture - is it p...
Customer experience | Sales, Customer Insights,...
Suggested answer

Form Capture - is it possible to use hidden lookup value?

(0) ShareShare
ReportReport
Posted on by Fubar 2,752

Have used Form Capture to get data from an external website and create lead/contact records - this is working well.

Have created some hidden text fields to capture extra data we need - this is working well

What I want to do now is have a hidden field on the form that has a static value - the field needs to map to a Lookup in Dynamics 365 Marketing a) is this possible to map to a lookup, b) if so, what value do I put  on the external web page form (anything special because its a lookup etc).

Thanks

(note: if manually creating the landing page from scratch in Marketing to achieve what I want, I would add a hidden lookup field and set a default value - in this situation the form has to be via Form Capture not manually constructed)

  • Suggested answer
    Defne Ayanoglu Profile Picture
    Defne Ayanoglu on at
    RE: Form Capture - is it possible to use hidden lookup value?

    Hi LA, 

    Have you figured this out? 

    You can try to do this by using it as a text box with default value and create CRM workflow that will translate this text value to a lookup.

    In the workflow, you can specify this: 

    [oncreate of contact] [if sourceformid=my form] [set lookupfield=some value] 

    Hope this helps, 

    Defne

  • cloflyMao Profile Picture
    cloflyMao 25,198 on at
    RE: Form Capture - is it possible to use hidden lookup value?

    Hi Luke Adams,

    Could the workaround work for you?

    Regards,

    Clofly

  • cloflyMao Profile Picture
    cloflyMao 25,198 on at
    RE: Form Capture - is it possible to use hidden lookup value?

    Hi LA,

    Currently only embedded form supports with look up field.

    A workaround is that you could create an optionset field Source form type and a simple line text field for Contact entity.

    The optionset field is used to indicate whether the contact is from the capture form, and we save name of lookup record to the text field.

    4188.JPG

    By default, the source form type could be set to "Capture form", and hide those two custom fields.

    Then create a flow, it only starts when the optionset equals to "Capture form", use value from the text field to retrieve mapping record of look up field,

    finally populate the real lookup field with retrieve id value. 

    Regards,

    Clofly

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans