Share
ReportHi,
We are using CRM 2016 online with two production server instance.
We are thinking to develop Pricing, Discount, Promo, Entitlement rule engine using Discount, Pricelist, PricelistItem entities. We also want to add recurring invoicing and subscription module using CRM workflows.
We are planning to use CRM actions as entry and exit point to read the rules and return output based on rules defined in pricelistItem entity. Every day we will be running thousands of renewal subscriptions which involve again calculating price, discount, entitlements for generating the invoice.
Generated invoices involve receiving payments from credit card and sending the invoice as an email to the customer.
I know that I am expecting too much from CRM actions and workflows and thinking that we will get the above functionalities without any substantial issue in future.
Please suggest whether this is the recommended best practice to develop the above functionalities in CRM and what major impact we may have on maintenance and performance?
Are we going to break the separation of concern and Domain driven design development rule if we follow this approach?
Thanks in advance
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
17,308
