on
RE:
Would be great if it could include an option to show the individual points as a jitter plot next to the box
RE:
by this option users are creating the queues and tracking mail to it
RE:
I feel this current logic of inventory aging report is not correct. it really gives false information
RE:
We also require Planning Optimization to plan for negative stock. Another feature Master Planning did that Optimized Planning does not and is causing major issues for our planning processes.RegardsSean
RE:
Need smaller font size than 8.. An absolute need when people are now using this tool more and more. Thanks
RE:
This is adding up to a top priority likely over 20 votes and counting when you sift through the other posts on segment editing, I know you have done some and working some so let's focus on the segment edits so we an break out logic and nest CI-J segments within each other and really use CI-JNote the A. is similar to several other posts on editing CI-J segments including another CI-J segment or in a Journey.
RE:
Accelerating this to release will be the "killer" feature for many customers who are either happy with their current cloud stack or sticking to Power BI directly over their on-premise SQL. Please implement this or incorporate transactional replication from on-premise SQL to the newly announced Fabric Databases.
RE:
This seems like it should be an easy fix that would save a lot of time and be more accurate to job costing.
RE:
We do need filters on grid.I'd say it's the most important feature needed. Grids are very important in real world to avoid export to Excel and filtering.
RE:
The 1st point is very critical. Any company with multiple branches will surely have stock transfers between locations. These transactions should not be taken as fresh stock inward. Stock should be considered as ageing until it is sold out of the company This should be simple logic to apply irrespective of the fact that product is with serial number or notConcur with points 2.3.4 alsoAn immediate solution will be appreciated