on
RE:
Agreed. Also, there should be no restriction on the count and combination of financial dimensions that can be used for single allocation rule and report.
RE:
I agree, either we need a fix or at least an amend to the documentation, we will collaborate on this with our stakeholders
RE:
Hi! Any progress on this idea?I think many companies are needing this functionality.
RE:
We need this new feature, as the current situation leads to unnecessary extra work and causes confusion in development.Additionally, obsolete tags should include information on the release in which the change will take effect. I cannot inform our customers when, for example, the "Package Tracking No." field will be expanded to Text[50]. Even though an obsolete tag states "24.0," we are currently in version 25.5. The preview versions of 26 and 27 still show a field length of 30, which creates significant issues for planning and communication.
RE:
There is nothing to track- Its a problem as if you use bidirectional sync you cant change order status to "submitted" and you cant actually get orders to Busines Central. So whats the point of this function or development if missing button or function makes it useless? Its wasted time and effort on this?Its likely that not many using Sales and BC together as there are allot of differences. Foe example you cant choose item variants in Sales when quoting - how on earth you can make relevant quote to customer if you cant understand if you have relevant variant in stock or not?Overall MS should focus on making basic sales function work. thise Sales spamming tools are fun but noone uses as they consume time and ROI is quesitonable.
RE:
This is a fundamental requirement as Accounts Payable functions that are outsourced by organisations do not allow for AP processors to access purchase order screens (other than display only). As a result, a requirement to add more work to a purchasing officer to add line items to manage credits by adding lines to a PO with workflows and a goods receipting performed by warehouse workers means we have involved up to 4 extra roles to fix what could be an AP processing error.Anything that can be done to expedite this development (as we are close to go live) would be welcomed and highly valued by our business.
RE:
Very common requirement for multi-level BOMs and Formulas!
RE:
We also have this issue.There appears to be no system settings to be able to set a different priority list for Mailbox selection than the standard one where Users is 1st and Queue related Mailboxes are 8th.We have had to add a Power Automate flow to check when this happens (trigger on Email receipt) to create Cases from the emails that should have gone to a Queue Mailbox.The only system way of doing it otherwise maybe ARC rule for every user mailbox.... Hundreds of them so that isn't a viable option.
RE:
We have done this by adding a default queue for email field to the user table, then using a Javascript on the Email form based on the Creator/Owner of the email. If the user has a default queue set for email, then change the from on the email.You cannot use the existing queue on the user and change to another queue, it breaks other stuff. Needs a new field.
RE:
This is dreadfully needed.