on
RE:
hgdhbvhxzbjvhcxz
RE:
The parameters ARE available to pass to an email that is triggered, but NOT to a pipeline or to a code notebook.Without this, Activators are simple useless for triggering pipeline or code is simply. The fact they are there for email should mean this is not a huge fix.I am amazed this is 4 months old and still not fixed.
RE:
I'm currently hitting a problem with the existing slicer capabilities. I have a table with multiple postcode values in it per row. I also have a lookup table with extra information about the postcodes, such as covered local authority, ward, etc. I offer slicers on several of these lookups per postcode value. The first I can do using a relationship. The rest, I have to use calculated columns in the main table to offer the slicers, causing extra weight in the model. I also display filter text for these columns showing what is selected, as I use a filter page and sync slicers as otherwise the filters would leave no space for the visuals. This creates a two-pronged request. Firstly, let slicers choose an inactive relationship to slice on instead of the default. Second, extend FILTERS, ISFILTERED etc. so they can specify which relationship is to be examined.
RE:
With the new Financial tag rules Preview since version 10.0.42 I am able to cover this now:Transaction entry Point 'Vendor invoice journal' and using the financial tag Invoice Number on the offset account. This also covers the financial tag value on each transaction in the accrual, so here I have the direct link now via standard D365FO.
RE:
6 years passed and still nothing! Shame!
RE:
It does not seem possible to change the font colour for advancedSlicerVisual in the .json theme file. It looks like it is defaulting to the "foreground" value in the theme file.
RE:
Enigineering change management workflows and others for operations can also be very interesting. For example: creation and acquisition of assets.
RE:
A cmk would be beneficial.
RE:
just make it like Excel :v
RE:
Overall, The way reservations work in D365 BC is way more complicated that it needs to be. There really is no need for reservations to be linked to the individual item ledger transactions that make up the sum of the inventory that is on hand, as all the items of a particular item and lot number combination should be identical to each other. It really does not matter which particular bin the stock gets picked from, because it's all the same. A simple reservation ledger that adds and subtracts reservations, tagged to particular item numbers and lots is all that is needed, with the system simply summing up the entries to determine whether there is, or isn't any available (unreserved) stock. The sheer unnecessary complexity of how reservations work has caused huge headaches for our vendor partner, and considerable development expense for my organization.