on
RE:
it's almost been 10 years now.. Who are we, probably not important enough in the eye of microsoft to implement such a small change
RE:
Our users are requesting to be able to post in batch for all types of FA journals,
RE:
This would be fantastic. We are restricted with how early we can assign Preventative Maintenance Jobs each month, so being able to preassign the RSO run to a specific date each month would be extremely helpful.
RE:
Still waiting for this...
RE:
Any update on this ?
RE:
I would like a toggle on each individual visual filter, so that before selecting visuals to capture their data state in a bookmark, I could set which individual filters to capture. This way, when activating the bookmark, only the filters selected when creating/updating the bookmark would change. If I have two sets of buttons impacting a same visual (e.g. "(A) new contrats / (B) existing contracts" on one hand, and "(1) won / (2) lost / (3) in progress" on the other hand), today I have to create a bookmark for every possible combination (6 in my example : A1, A2, A3, B1, B2, B3) ; with bookmarks impacting only selected filters, I could reduce that number (5 in my example : A, B, 1, 2, 3).
RE:
This is very much needed for correct forecast consumption. How can it NOT consider picked/deducted/sold sales InventTrans records when doing forecast consumption? That is just ludicrous to think what it is currently doing is correct. No logical human being would think this is correct.
RE:
@admin: Which reversals settle upon posting? Thanks
RE:
It makes great sense to add this feature on sales, especially since the GLN field is already there on the alternative Ship-To adresse.Alternatively, that the GLN field on the customer is changed to a drop-down field, and where the one selected on the customer card is the default, but then the value can be changed on the salesorder/invoice.
RE:
I encountered a different scenario today where this would be useful: I created a field parameter. I want the options in the slicer to have a different name compared to the table. So the slicer would show "Full Detail" and "Rollup", while the table should name them "Split" and "Split Rollup". In other words, the slicer offers the options showing what the field _does_, while the table shows the actual field name. Right now, the parameter seems to control the field name in the table. If columns can set their own title, they should be able to receive information on if a parameter field name is overriding the default. The function could then choose to accept or reject this override.