Dynamics 365 offers various ways to uniquely identify and display records, which are important for data integrity, performance, and user experience. In this article, we'll explore the differences between Primary Key, Alternate Keys, and Primary Column, along with examples for each.
JavaScript can be employed in Dynamics 365 to enhance the presentation and functionality of columns in entity views. By using a Web Resource and specifying a JavaScript function, you can achieve various types of custom formatting and actions.
Out-of-the-Box (OOB) Command Actions in Microsoft Dynamics 365 offer a range of functionalities designed to facilitate various business processes. In this article, we delve into some of the key OOB Command Actions, providing detailed descriptions, typical usages, and practical examples for each.
Description:
Moves an entity record into a queue.
Usage:
Often used in customer service scenarios for triaging and categorizing incoming cases.
Examples:
Description:
Adds a user to the access team of a specific record.
Usage:
Primarily used for facilitating collaboration on specific records.
Examples:
Description:
Applies a routing rule to an entity record.
Usage:
Typically used in customer service settings to assign cases to specific queues based on attributes like priority, type, or service level.
Examples:
Description:
Calculates the actual value of an entity record, typically used for financial records like Opportunities.
Usage:
Used to re-calculate the actual financial value of an entity based on various criteria.
Examples:
Description:
Changes the status of an Opportunity to "Won" or "Lost."
Usage:
Used in sales pipelines to formally close out opportunities.
Examples:
Description:
Completes a Sales Order, transitioning it to a "Fulfilled" status.
Usage:
Used in order processing and management.
Examples:
Description:
Generates Quote Products based on an existing Opportunity.
Usage:
Used in the sales process to convert opportunities into quotes.
Examples:
Description:
Generates Sales Order Products from an Opportunity.
Usage:
Often used to automate the transition from a closed-won opportunity to the creation of a sales order.
Examples:
Description:
Locks the pricing on an Invoice, making it uneditable.
Usage:
Used for financial compliance and to prevent unauthorized changes.
Examples:
Description:
Locks the pricing on a Sales Order.
Usage:
Used to ensure pricing consistency and compliance after receiving customer approval.
Examples:
Description:
Converts a Lead into an Opportunity, Contact, and/or Account.
Usage:
Used in sales and marketing to move a lead to the next stage of the customer journey.
Examples:
Description:
Removes a user from the access team of a specific record.
Usage:
Used to restrict access to records when necessary.
Examples:
Description:
Closes an Incident (or Case) record as "Resolved."
Usage:
Used in customer service workflows to close cases that have been satisfactorily resolved.
Examples:
Description:
Changes the status of a Quote to "Accepted" or "Declined."
Usage:
Used to formalize the outcome of a quoting process.
Examples:
Description:
Reverts a closed Quote back to an "Active" or editable state.
Usage:
Used to make changes to quotes that have already been closed.
Examples:
Description:
Applies a pre-defined Word template to an entity record to generate a document.
Usage:
Used to automate document creation in various business processes.
Examples:
Understanding and effectively using OOB Command Actions in Dynamics 365 can significantly streamline your business processes. These actions are integral components that can be invoked through workflows, custom code, or Power Automate flows, enabling greater automation and efficiency.