> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/integrations/dynamics/5355-2.md). # Installing Dynamics Contact Panel The Contact Card is an embedded panel that matches records by email. It looks up the Dynamics record's primary email in eMarketeer and shows the corresponding contact information without leaving Dynamics. ## Prerequisites Before you begin: * Your eMarketeer account must be connected to Dynamics 365. If you have not connected yet, follow the Dynamics 365 Installation Guide. * The Contact Card web resource is automatically created in your Dynamics environment when you connect. No manual installation is needed. * You need the System Administrator or System Customizer role in Dynamics 365 to add the web resource to forms. ## Adding the Contact Card to a Contact form These steps use the modern Power Apps form designer. 1. Sign in to Power Apps and verify you are in the correct environment. 2. In the left navigation, select **Tables**, then open the **Contact** table. 3. Select **Forms**, choose the **Main** form you want to edit, and click **Edit**. 4. In the form designer, open the **Components** pane on the left side. 5. Expand the **Display** section. 6. Select **HTML Web resource**. 7. Find **eMarketeer Contact Card** in the list and click **Add**. We recommend placing it in a dedicated section or tab for a clean layout. 8. Select the web resource on the form to open the **Properties** pane on the right. 9. Configure the display properties: * **Hide label:** Enable (recommended for a cleaner look) * **Component height:** Set to 8–10 rows (approximately 300–400px) * **Scrolling:** As Necessary * **Display border:** Disable (for a seamless embedded look) 10. Scroll down to the **Advanced** section and configure: * Enable "Pass row object-type code and unique identifier as parameters" * Disable "Restrict cross-frame scripting where supported" 11. Click **Save**, then click **Publish**. "Pass row object-type code and unique identifier as parameters" is required. Without it, the panel cannot identify which record you are viewing and will show "No record context available." "Restrict cross-frame scripting where supported" must be disabled. When enabled, it blocks the JavaScript that the Contact Card needs to function. Open any saved Contact record to verify the eMarketeer Contact Card appears and displays data. If you are using the classic form editor instead of Power Apps, select the **Insert** tab on the ribbon, then click **Web Resource**. The configuration options are the same but appear in a dialog box with tabs (General, Formatting, Dependencies) instead of a side pane. ## Adding the Contact Card to a Lead form The same web resource works for both Contact and Lead forms. Follow the same steps as above, but open the **Lead** table instead of the **Contact** table in step 2. The Contact Card reads the entity type automatically, so no additional configuration is needed for Lead forms. ## Using the Contact Card When you open a Contact or Lead record that has the Contact Card on the form, the panel loads automatically. It retrieves the record's primary email address and looks up the corresponding contact in eMarketeer. What you may see: | State | What it looks like | What it means | | ---------------------- | -------------------------------------------------- | --------------------------------------------------------------------------- | | Loading | "Loading eMarketeer…" (gray centered text) | The panel is loading. Wait a few seconds. | | Contact card with data | eMarketeer contact information | The record's email was found in eMarketeer. | | No matching contact | Empty panel or "no contact" message | The email on this Dynamics record does not match any contact in eMarketeer. | | No record context | "No record context available" (gray centered text) | The panel cannot identify the current record. See Troubleshooting below. | The Contact Card only works on saved records. If you are creating a new Contact or Lead, save the record first. Dynamics does not pass the record information to the panel until the record is saved. ## Troubleshooting | Symptom | Cause | Solution | | --------------------------------------------- | ------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Web resource not found in the Components list | The connection may still be processing | Wait 2–3 minutes after connecting, then refresh the form designer. The web resource is created automatically during the connection process. | | "No record context available" | "Pass row object-type code and unique identifier as parameters" is not enabled | Edit the form, select the web resource, and enable this setting in the **Advanced** section. Save and Publish the form. | | "No record context available" on a new record | The record has not been saved yet | Save the record first. Dynamics does not pass the record ID to web resources until the record is saved. | | "Loading eMarketeer…" stays indefinitely | Network or authentication issue | Verify the Dynamics user has internet access to app.emarketeer.com. Open the browser developer console (F12) and check the Console and Network tabs for errors. | | Panel is blank or shows an error | "Restrict cross-frame scripting" is enabled | Edit the form, select the web resource, and disable "Restrict cross-frame scripting where supported" in the **Advanced** section. Save and Publish the form. | | No contact data shown | No matching contact in eMarketeer | The panel matches by email address. Verify the Dynamics record has an email in the **Email** field, and that the same email exists as a contact in eMarketeer. | | Panel missing after reconnecting | Web resource was removed during disconnect | After reconnecting, the web resource is recreated automatically. You may need to re-add it to the form by following the steps above. | ## Related articles * Dynamics 365 Installation Guide * Legal Basis & Subscription Sync * Importing Contacts from Dynamics * Journey Steps --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://support.emarketeer.com/integrations/dynamics/5355-2.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.