Solution:<\/strong> If you have worked with custom service module earlier then you might be aware of the Case Origin (caseorigincode) field which is a option set field. This field is used to configure case origin, for example if case is reported through phone, email, web etc. We can reuse this field to identify if case is reported from the Customer Portal. Let’s see how we can implement this using following steps:<\/p>\n 1. First add an option for Portal in case origin field, navigation to Settings->Customizations-><\/strong>Customize the system<\/strong> from top navigation bar. Hope it will help someone!!<\/p>\n","protected":false},"excerpt":{"rendered":" Sometime we may need to set default value for the entity field in portal forms. In this post we are going to discuss, how we can leverage entity form metadata to fulfil this requirement. Requirement: Identify if case is created from Dynamics 365 Portal. Solution: If you have worked with custom service module earlier then you might be aware of… Read more »<\/a><\/p>\n","protected":false},"author":1,"featured_media":3037,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[402,522,508],"tags":[503,542,545,544,543],"_links":{"self":[{"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3079"}],"collection":[{"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3079"}],"version-history":[{"count":7,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3079\/revisions"}],"predecessor-version":[{"id":3093,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3079\/revisions\/3093"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/3037"}],"wp:attachment":[{"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3079"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3079"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/himbap.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3079"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n2. Navigate to Fields<\/strong> under Case entity and open case origin field.
\n3. Click on Edit<\/strong> button and add new option for Service Portal
\n![\"case1\"](\"https:\/\/himbap.com\/blog\/wp-content\/uploads\/2018\/07\/case1.png\")
<\/a>
\n**Keep note of value of the Service Portal<\/strong>
\n4. Save and publish your changes.
\n5. Navigate to Portals->Entity Forms<\/strong> from top navigation bar.
\n6. Open your case entity form and Navigate to Entity Form Metadata<\/strong> section
\n7. Click on +<\/strong> sign, to create new Form Metadata<\/strong> record
\n8. Set Type<\/strong> as attribute and set attribute name
\n<\/a>
\n9. Navigate to Set Value On Save<\/strong> and use following option
\n<\/a>
\n**Make sure the value is matching to your Service Portal option value<\/strong>
\n10. Save and Close your changes.
\nNow when you will create case from Portal, case origin will be set as
\n<\/a><\/p>\n