|
Current Version: 9.5 |
|---|
Dynamics용 Adobe Sign v9.3.x 지원은 2021년 11월부로 만료되었습니다.
- 모든 패키지 버전은 가능한 한 빨리 최신 버전으로 업그레이드되어야 합니다.
- 9.3.x 이하 버전에 대한 액세스는 2022년 3분기에 완전히 끊길 예정입니다.
참고로 이러한 업그레이드 요건은 통상적인 통합 수명 주기에 대한 예외이며 이는 적용되는 업데이트의 특성으로 인한 것입니다.
MS Dynamics Online documents:
MS Dynamics On-Prem documents:
Common Questions
-
Sign in to MS Dynamics.
-
Navigate to Settings > Customization.
-
Click the Customize the System option.
-
In the left navigation pane, click the required custom entity.
For example, Yukti_test. -
To display the fields and controls, click the name of the Entity.
-
Navigate to Forms, and then click the Information link associated with the Main form type.
-
Add New field and enter the name of the field.
-
Save and close.
-
Drag-and-drop the field in the Entity, and then Save and publish all customization.
-
Sign in to MS Dynamics.
-
Navigate to Settings > Customization.
-
Click the Customize the System option.
-
In the left navigation pane, click the required custom entity.
For example, Customer.
-
To display the fields and controls, click the name of the Entity.
-
Copy the value from the Name field (for example the value is new_customer).
It is the internal system name of your custom Entity. -
Navigate to the 1:N Relationships option, under your custom Entity.
Click the New 1-to-Many Relationship button. -
Create the relationship:
- Choose Agreement from the Related Entity field.
The Name field changes to show {entityName}_adobe_agreement. - Paste the name of your custom entity, for example, new_customer, in the Display Name field.
The Name field changes its value to “new_” + {entityName} + “Id”. (new_new_customerID).
c. Click Save and Close.
The Relationship window closes.d. Click Publish All Customizations at the top of the 1:N Relationships page.
- Choose Agreement from the Related Entity field.
There is a known issue for On-Premises CRM environments that have a multiple server setup (CRM is on one server and DB is on another server) and their SPN is not configured correctly.
This results in the Admin Settings page showing up blank.
The best solution to this issue is to contact Microsoft Dynamics Support and enlist their support in configuring the SPN correctly.
A brief overview of the SPN configuration can be found here.
A workaround to the problem for most environments:
- Download the Microsoft Dynamics CRM SDK
- Run MicrosoftDynamics365SDK.exe
- Find and run the Plugin Registration Tool (SDK\Tools\PluginRegistration)
- Connect the Plugin Registration Tool to your Dynamics instance (click here for instructions)
- Browse the AdobeSign assembly
- Specify the Isolation Mode as None
- Click the Update Selected Plugins button when done
If this workaround does not solve the problem, contact Microsoft CRM Support to investigate the SPN for your environment.
Once the SPN issue is resolved, the Isolation Mode setting can be returned to Sandbox.
A sender is getting the following error while sending a record for signature. They get the error when the agreement record is created.
The error appears when the sender goes to more options and then clicks “Send for signature”. The issue occurs only in a production environment where the application security (F5) and load balancers are set up.
Answer:
When the managed solution for Acrobat Sign is imported in CRM, the associated plug-in libraries are registered under the isolation mode: sandbox. This causes problems in production environments. Manually update it to “None”.
Issue:
The following errors show up when importing Microsoft Dynamics v6:
Errors:
- “The import of solution Adobe Sign failed”
- "A SQL Server error occurred. Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization's Microsoft Dynamics CRM Administrator. Finally, you can contact Microsoft Support"
Cause:
The error during solution upgrade points to the SQL server error, which means there is a traffic overload in CRM’s DB connection or SQL server is in a bad state.
Resolution:
- CRM admin should inspect CRM server’s application Event Log to see if any other error can be seen there that could point to SQL server issues.
- Manually drop fulltext index on adobe_agreementBase and on adobe_agreementtemplateBase tables in SQL server.
