0
Category:
STATUS DETAILS

Comments

People don't want to have to use Projects to capture customer deposits. We should be able to have deposits for sales order lines and even payment plans for lines. Functionality was there but was removed in 10.0.14 because it was originally created for Retail. Anyone selling custom or make-to-order or configure-to-order products, needs the ability to capture deposits.

Category:

This is definitely needed! Reports would be soooo much nicer, especially for those moving from GP/Management Reporter.

Category:

Please include support for fields having code in the OnLookup trigger too.
E.g. the 'Primary Contact No.' on the Customer table does not support the new peek experience. (According to MS Collaborate, it's by design)

Category:

This is an absolute must... The current setup of subscription center doesnt make sense... Uncheck 1 box and check another for global unscubscribe...
Bad design.. and not very user friendly.

Category:

It is a common requirement and that's out of box in SAP and Oracle.

Category:

Fully agree, I have got that requirement several times and we had to use an external netting system.

Category:

Hi, it would be good also to have Up-sell/Cross-sell functionality on Sales Quotations.

Category:

Very good suggestion, this would make using form level double opt-in much more useful (=possible).

Category:

Much like the purchasing functionality with relation to vendor warehouses, when transferring material to a warehouse with the Reference - Vendor Account field populated, the address and GST information should be pulled from the Vendor account to allow GST to be calculated. This is a vital part of the Transfer process and is needed ASAP.

Category:

Another couple of reasons why the alternative solutions that you could use for this are less than ideal:
1.) Any other solution would rely on the creation of a Word document from a Word Template and the Word document getting saved against a record in CRM. So there are storage issues there - why generate the Word document if it's never going to be used except to generate the PDF. The current solution allows for the creation of a PDF without having to go through the interim Word document, and can be done entirely in memory, so no storage required if the PDF is just going to be printed or emailed.
2.) All other solutions that I've looked at require a Workflow or Flow to fire whenever an annotation is created in CRM. But this means that every note that gets created in CRM will result in a workflow firing, even if the note doesn't even have an attachment, or even if the attachment is not of the type which will get turned into a PDF by the flow. This is massively inefficient, and could result in thousands of flows/workflows firing which are doing nothing useful at all.

Category:

  • 1
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 492
  • 493
  • 494
  • 500