Liquid error: Value cannot be null.
Parameter name: key
Microsoft Dynamics 365
In our solution the rules for Service lines are set up in a Service Agreement. The Service Agreement is a custom entity with specific rules how to override the default price list. In theory there could be as many Service Agreements and Pricing rules as there are Customer Assets, but we are trying to harmonize.
It will not be possible to create a common pricing solution that satisfies everyone.
It would be nice to be able to set up more Resource Pay types and to have a parameter to indicate if the Pay type should generate a WO Service line from the associated Booking Journal.
The need for automatically created WO Service lines is derived from the fact that the WO Invoice within CE is based on WO Service Lines and WO Product lines. This in turn, is required since Time, Fee and Expenses are Non-Inventory Products I Field Service.
On the wish list is an introduction of transaction types in FS for Time , Fee and Expense as in PSA and FO and to get rid of WO Service lines. For a company like our, that is using both PSA and FS integrated to FO it would be more logic and robust solution.
I totally support your idea and what you higlighted.
In addition, considering some companies have a lot of book sections, the effort to change the sequence code and the book sections set up every year is high.
Making automatic the change of number sequence between years will surely help.
This request is a no brainer for me and I'm not sure why it needs votes, surely it needs understanding of compensation. HR should be able to edit as standard so as not to disturb comp history, however variable comp also need a start and end date. We have people who move from Bonus to Commission and without an editable end date, it stays active even though that plan isn't. We have reverted to add a new bonus level of 'zero' to compensate but that is so messy
without this function it adds a lot more 'admin' to the process. You don't need to change the process as such, just add a tick box to enable continuity of salary from one role to another
This is absolutely essential! Should not be an idea, its a standard HR requirement
This topic is also related to the idea: Intercompany share warehouse locations
Checked against current version - it's not fixed - Button Label still says "Geöffnet" - was there a problem submitting the fix?
Installierte Produktversion : 10.0.12 (10.0.507.10024)
Installierter Plattformversion: Update36 (7.0.5688.35584)
I agree I do not want to automate posting to my personal page but to my company page.
The lack of the ability to copy a sandbox when creating a new sandbox or exporting a company from a sandbox is a serious limitation to the cloud product which leads to a flawed development and code promotion process. The standard development process is to separate the development, test, and production databases. Once development of a task is complete, the code is promoted from development to test. Developers should be doing initial unit testing before promoting changes to test. The development database tends to have limited data which prevents proper testing by the developer. This has led to developers developing in test or promoting unfinished or untested changes. Clients are trained to test in test to confirm functionality before it is promoted to production. Customers are running into errors in partially developed solutions and messages that the administrator has made a change and have to close and reopen as developers promote new code.
Using configuration packages to export all data in all tables is not a viable solution. The import/export time is prohibitive and the time it takes to build the configuration packages is prohibitive.