10
We need a way to easily create pricing dimensions.
It took me 24 hours to understand (lots of errors, missing steps there) to implement a pricing dimension using MS instructions.
I know PO is more involved but I think if we can make this an easy setup (without creating a separate solution), it will make life easier and make the system more approachable for everyone.
In many countries and states, they have different laws regarding overtime pay and if we really want a full-on enterprise project tracker, we need to have this capability. In this day and age, Customers just don't understand why this is not OOTB feature.
Please, consider it.
Juan Simon
It took me 24 hours to understand (lots of errors, missing steps there) to implement a pricing dimension using MS instructions.
I know PO is more involved but I think if we can make this an easy setup (without creating a separate solution), it will make life easier and make the system more approachable for everyone.
In many countries and states, they have different laws regarding overtime pay and if we really want a full-on enterprise project tracker, we need to have this capability. In this day and age, Customers just don't understand why this is not OOTB feature.
Please, consider it.
Juan Simon
STATUS DETAILS
Needs Votes
Comments
The documentation still is not clear, it took me more than 24hrs to understand and make the dimension work. Our case was for "overtime" which should be something straightforward. Would be helpful if the Time Entry (msdyn_type) field would be available as a dimension as it happens with "bookable resource".
To customers, simplicity would be highly beneficial. Even users who have worked with the current system and approach are eager to have more straightforward manners to create price dimensions!
Rupa Mantravadi (administrator)
Juan Floriani Simon, An extremely valid suggestion. Will defintiely take it up for consideration once it has more support.