Microsoft Dynamics 365
Project Operations finds the correct role prices (sell and cost) for a task, quote line detail, contract line detail, and actuals using pricing dimensions. It would be useful to have an API we can invoke in custom code or perhaps as an action to provide these. Specifically, we would like to calculate the revenue and cost associated with a booking for forecasting purposes.
Currently a user has to use separate mobile apps for Expense Entry in UO and Time Entry in Project Operations. They should be able to use just a single mobile app.
Currently (Q12021) we have a banner warning in the als CRM interface (Advanced Settings) that asks us to migrate
-Automatic record creation aand update rules
-Service Level Agreements
in the legacy web client to the Unified Interface (before October 2012)
Please migrate your items to Unified Interface
When I choose Migrate Now it shows all 0's on both categories, so I chose Start Migration to run 'nothing' through and to get rid of the warning.
In the next screen I have to select the two categories, but because MS put in a rule NOT to proceed 0's , the NEXT button is not allowed for clicking.
Please add a pre-condition on the Upgrade warning to check if their are any items to migrate and if not, don't let it pop up anyways. Else, allow for Next on 0 items and get te whole thing over doing nothing.
In our organisation there are colleagues who manage employees with restricted compensation plans, and cannot request a compensation change for them, but can still view their salaries. I think it would be a great idea for managers to continue to see the salaries of their reports, but be able to request a compensation change for them despite not having access to the compensation plan in the back end of the system.
Great Idea! Would improve master data accuracy. I have spend some working days correcting master data for a customer. With this service the data would have been correct and my customer wouldn't have any master data errors in the ISO20022 files. And I will not miss doing these kind of clean up tasks in the future :-).
there are words missing in the example... second try :
for example AP :
vendor invoice posting date 01/02/2021 - period 02/2021 is open, period 01/2021 is closed (or module vendor)
Ledger accrual 12M starts from 01/01/2021.
Posting will fail because of first period closed.
Workaround MSFT : open period 01/2021 + close module vendor , create GL journal with ledger accural posting --> this is a cumbersome process
It is relatively straight forward to do the calculation for them
Number of contacts x 10 emails per month x 12 months = total emails per year.
The issue comes if you have 100,000 contacts that you want to reach out to once a month, rather than 10,000 contacts you want to reach out to 10 times a month. Then the argument breaks down.
Please remember, that ClickD is priced on email sends per year, where as MS Marketing is priced on Contacts where each contact can have 10x emails per month.
ClickD cheapest package is $650 per month for 200,000 email per year or 16,000 per month. Also using ClickD over time takes up quite a lot of storage space in your Database table which you will eventually start to pay for per GB per month. This must be taken into account.
MS Marketing is $750 with first 10,000 Contacts included (10,000 x 10) = 100,000 per month x 12 = 1,200,000 emails per year.
Also, you don't pay for Contacts in your database which are not Marketing related so it's not all the Contacts in your system but just a subset. While I agree that on the surface MS Marketing seems expensive it is comparable in the market for what you get. There are a lot of Azure services used by Marketing so the costs of this must be covered.
I think this is a duplicate of https://experience.dynamics.com/ideas/idea/?ideaid=f88fb471-6507-ea11-b864-0003ff68ac6b
If any vendor is having dual TDS transactions, one in lower TDS rate and another in normal TDS rate under different section and TDS is wrongly deducted in lower TDS code then to reverse the same, withholding tax journal is required with lower TDS functionality