• Resolved nmoriarty

    (@nmoriarty)


    I have a site pulling a form that uses some custom views for drop downs. It was working when I was using the msdyncrm_form tags that are now deprecated. I have changed it to use twig, but it just pulls in empty drop downs now. My code is

    [msdyncrm_twig]
    
    {% form entity="incident" name="Web To Case" mode="create" message="Thanks!" hide_form="true" lookupviews={"customerid":"Case Accounts","am_application":"Active Applications"} %}
    
    {% endform %}
    
    [/msdyncrm_twig]

    Am I not using the lookupviews attribute correctly? It looks like I have it exactly as the documentation says to structure it, and they do show up as drop downs when I add this, they are just empty now. Would appreciate any help I can get with trying to get these drop downs to get filled the way they were with the deprecated tags.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author alexacrm

    (@alexacrm)

    Hi @nmoriarty,

    syntax looks fine. We’re investigating.

    Cheers

    Plugin Author alexacrm

    (@alexacrm)

    Turns out, the documentation has a bug in it and the syntax is slightly different. The value is the array of the entity and the view (to handle Customer and Regarding fields that support multiple entities). So the correct syntax would be:

    
    lookupviews={"customerid": ["account", "Case Accounts"],"am_application":["am_application", "Active Applications"]}
    

    (I assumed your custom entity is am_application and the lookup is also am_application)

    HTH

    • This reply was modified 6 years, 3 months ago by alexacrm.
    Thread Starter nmoriarty

    (@nmoriarty)

    That was it. It is all pulling in correctly now after changing that. Thank you for the quick response.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Lookup Views not Being Pulled In with Twig’ is closed to new replies.