0
Category:
STATUS DETAILS

Comments

The functionality that was added to the Item Journal is great. It would be nice to add this functionality to Purchase Order and Sales Order Lines as well. It would make data entry so much simple in a lot of cases.

Category:

Any update on this release? It is mentioned that it should have been part of the 2023 release wave 1 but I cannot see it.

Category:

Even more detail: ”Creating a FastTab is easy. A FastTab is a group control directly within the content area of a card, document, or task page.”In the Content area of the hosting page, parts can only be collapsed if they satisfy the following rules:parts are hosted on a task dialog, card, or document page.parts aren't placed within a FastTab.”(1) This means that they have to be their own group and cannot be part of another group "When placing two ListParts in a group, they share horizontal space." (2) This is the only way to have parts side by side(1) + (2) = It’s impossible to have them side by side and also be collapsable/expandable. As for the actions issue: In the Content area of the hosting page, parts will only display an expanded action menu if they satisfy the following rules:parts are hosted on a card or document page.parts aren't placed within a FastTab.”Meaning again, that it's impossible to have them side by side and also have promoted actions.

Category:

Users complain a lot about this behavior, and they can't understant why opportunity and appointment don't work the same way

Category:

This is not only a useful improvement, but also an alignment with the product, since it works well on Opportunity, for example! +1

Category:

Yes this would be great, if it could be realized.

Category:

Would be great if line description could be added as %7 placeholder code. That way we keep the option open for the client to choose their own specific combination for the booking description.

Category:

For us this is also really an issue.Is this still on the roadmap or do we need to customize?

Category:

This is useful for Australian market for integration with local tax authority ATO. As of today we can only generate the Australian BAS and the E-BAS.

Category:

Not sure what the status is on this from but here are some of my own observations as the planned cross dock partially works as detailed in scenario 1, this should be on the roadmap to fix. Scenario 1. Purchase order is created Sales order created Automatic Released to WH runs (including Planned Cross dock)Load is created and planned crossdocking is created Now a voyage is created for the PO PO invoice postedVoyage line status is GITAt this point you will notice that 2 GIT orders are created, 1 for the planned cross dock amount and 1 for the remaining inventory.Receiving the 2 individual GIT orders results in crossdocking work created as per usual . Scenario 2. Purchase order created Voyage created Sales order created Automatic Release to WH run with cross docking No planned crossdocking created.  

Category:

  • 1
  • 490
  • 491
  • 492
  • 493
  • 494
  • 495
  • 496
  • 497
  • 498
  • 500