It's great to hear that your customer is interested in utilizing approvals in the CRM with a hierarchical structure. In Microsoft Dynamics CRM, you can indeed set up multi-level approvals with a hierarchy. The specific steps and options may vary depending on the version of Dynamics CRM you're using, but I can provide some general guidance. In your CRM, create an approval process. This process will define the steps and the order of approval. You can configure the Line Manager approval as the first step and Director approval as the second step. Ensure that you have the appropriate user roles and permissions set up in CRM data enrichment. Line Managers and Directors should have the necessary permissions to approve or reject requests.Before deploying this setup in a production environment, thoroughly test the approval process to ensure it works as expected.
Check your CRM system's configuration settings to ensure that duplicate statuses are not allowed. Some CRM systems provide options to enforce unique values for specific fields. Verify that such settings are enabled for the activity status field. If your CRM system is integrated with other applications or databases, it's possible that duplicate statuses are being introduced during data synchronization. Review the integration setup and mappings to identify any issues that might lead to data enrich or duplicate.
If you haven't already, reach out to the support team or community forums for IFS to inquire about exposing the objversion field in the client API. They would be the best source of information regarding the feasibility of this request and any potential reasons why it may not be currently available.If the objversion field is not accessible through the client API, consider exploring other APIs or customization options provided by IFS. They may have additional interfaces or extension points that allow you to access the desired information.
You could create a new user role in your CRM system that grants sales reps access to make b2b data enrichment changes at the Category = Prospect level while still restricting their ability to make changes at the Category = Customer level. You could then assign this new user role to your sales reps as needed. You could modify the existing user roles in your CRM system to grant sales reps access to make changes at the Category = Prospect level while still restricting their ability to make changes at the Category = Customer level. This would require a more granular approach to permissions, but could be more efficient if you have a large number of sales reps. You could use field-level security to restrict access to specific fields within your CRM system. This would allow you to grant sales reps access to make changes at the Category = Prospect level while still restricting their ability to make changes to specific fields at the Category = Customer level.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
