[Mark Yankovich]

We receive quotes from several customers that are bidding on the same end project (see the example below).  From what we’ve tried in AX, quotes can only be tied to opportunities for the same customer.  This is not how our business is most typically done.  We believe there are other companies out there like ours using AX and would like to hear from you as to how you are accomplishing this.  Here is a quick example:

Main Opportunity by Customer Name/Project Name and expected revenue:

OP-0001 Company A has a New Building Project   Revenue $75,000

Associated Quotes by Customer Name and Quote Value (each of these are bidding directly for part or all of Company A’s project)
     QT-0001 Company B for $75,000
     QT-0002 Company C for $85,000
     QT-0003 Company D for $110,000

               ~ To be clear, the quotes tied to the opportunity will be from potentially several different existing customers.

We are on AX 2012 R3 CU13.

#AX2012
#Functional
#Intermediate

Thank you for taking time to read this!
??

——————————
Mark Yankovich
Allegheny Bradford Corporation
PA
——————————

[Rowland Keable]

We are an AX2009 user at the moment but are in the last stages of moving to D365 F&O and CE.  We had the same problem as you when we installed AX2009, namely that we have multiple Quotes against a single Opportunity.  Each of these Quotes is for a different company.  We supply the building trade effectively and so in that trade you will have multiple businesses tendering for a job.  The architect has specified our product so each of these tendering companies must come to us for a Quote, but there is only one Opportunity and only one of the Quotes will win (or they will all lose).  The Quotes may vary slightly either in price because of the volume of sales to that business per year affecting discount levels or in the list of parts if the business is trying to differentiate itself slightly.

We had to have the Opportunity and Quote part of the CRM module in AX2009 modified by our system integrator.  We also need to be able to create revisions of each of these Quotes to cope with changes in the requirements from the Architect.  So we can end up with 5 Quotes each with 3 revisions for one Opportunity.

Now we have had to have F&O modified in a similar manner and CE modified as well.

So I am afraid your only choice is bespoke modifications to the code.

#AX2009
#Functional
#D365

??

——————————
Rowland Keable
Searchlight Electric Ltd (illuma Lighting)
Castle Donington
——————————
——————————————-

[Mark Yankovich]

Rowland,

Thank you for your response.  Modifications are something we try to avoid.  Hence the reason for the post in hopes of finding others like us or an ISV that might have a solution.

It seems your modification has been successful.  From a first thought, it appears it could be a simple modification but we know how that can grow legs if not thought through enough.  We are very new to Dynamics and not sure we can guide an integrator to be sure all bases are covered.  Based on your experience what other areas need considered should we go the modification road?  What was the impact on out-of-the-box analysis and reports with the modification?

Still, we wonder why such a limitation was done by design.  To know this is still the same in D365 is very valuable information for us as well.

Stay safe!

——————————
Mark Yankovich
Allegheny Bradford Corporation
PA
——————————
——————————————-