When you need to display data on point-of-sale receipts that isn’t available in the standard receipt designer, you’ll need to create a custom field. This involves work in both Dynamics 365 (the backend) and the Retail SDK (the POS application layer). This walkthrough covers adding a custom field—using item barcodes as an example—though the pattern…
Filtering dependent fields based on parent field values is a common requirement in Dynamics 365 CRM. This guide walks through implementing conditional filtering so the salutation dropdown only shows values relevant to the selected gender. Prerequisites Access to a Dynamics 365 environment (2016 or later) with customization rights Basic understanding of option sets and form…
Filtering a dependent lookup field based on another lookup field’s value is a core requirement in Dynamics 365 and Power Apps. The classic example: a Lead entity with Branch and Sub Branch fields where Sub Branch options should only display records matching the selected Branch. The form editor handles this natively—no plugins or JavaScript required….
Converting a managed solution to unmanaged in on-premise Dynamics CRM requires direct database modification. You’ll need this when customizing third-party solutions that the publisher hasn’t provided in unmanaged form, or when you need to export and modify components before deployment. Prerequisites Full database backup (this modifies system tables — non-negotiable) SQL Server Management Studio or…