Dynamics 365 Project Operations

The Revenue Project ID field (Project management and accounting → All projects → Project → Revenue recognition) is designed to give flexibility in how revenue is recognized. When several sub‑projects roll up under a parent project, assigning the parent’s Revenue Project ID to each sub‑project allows the system to combine revenue recognition entries across all those related projects.

If each sub‑project uses its own Revenue Project ID, running revenue recognition will consume only one number from the voucher number sequence.

However, when multiple projects share the same Revenue Project ID, the revenue recognition process consumes voucher numbers based on the number of projects included under that Revenue Project ID.

Example:

If the current voucher number is PPV_0015, and you have 15 sub‑projects all mapped to the same parent Revenue Project ID, posting revenue recognition will generate vouchers up to PPV_0030.

It would be very helpful if the system provided a way to track which voucher numbers were consumed during this process, or an option to prevent this kind of voucher number “skipping” from occurring.

In the current design of the Project management and accounting module in the Finance and Operations application, when a purchase order is linked to a project, users are prompted to decide whether the vendor’s default financial dimensions on the purchase order header should be overridden with the project’s default financial dimensions.

However, there is no option that allows users to retain the default financial dimensions for item lines. As a result, users must manually restore the item-level financial dimensions, which is both inefficient and time‑consuming.

We would like to formally request a design enhancement to introduce an option that allows users not to override the item’s default financial dimensions when adding lines to a project purchase order.

本内容はSRチケット「2512150010000489」にてお伝えした内容です。

現象

Project Operations の見積もり画面で「概要」タブの顧客を変更すると、「顧客」タブに新しい顧客レコードが追加され、既存の顧客レコードも残るため、請求分割率の合計が 200% になります。

この状態で見積依頼明細行を追加すると、同様に顧客レコードが複製され、請求分割率が 200% のままになります。

さらに、この状態で「受注としてクローズ」を実行すると、

「見積もり依頼明細行の顧客設定が無効です。このアクションを完了する前に、見積もり依頼明細行の顧客設定のエラーを修正してください。」

というエラーが発生します。

問題点

• ユーザーは分割請求を意図しておらず、単純に顧客を修正したいだけなのに、分割請求前提の動作になってしまう。
• 請求分割率が 200% という不整合な状態が自動で作られ、ユーザーが気づきにくく、後続処理でエラーとなる。
• 単一顧客のシナリオで、分割請求ルールが残る仕様は直感的でなく、使い勝手が悪い。

要望

• 「概要」タブで顧客を変更した場合、既存の顧客レコードを残さず、新しい顧客に置き換える動作にしてほしい。
• 少なくとも、請求分割率が 200% になるような不整合な状態を自動で作らない仕様に改善してほしい。
• 分割請求を行う場合は、ユーザーが「顧客」タブで明示的に追加する操作に限定し、顧客変更＝分割請求という解釈をやめてほしい。

背景

この事象はユーザーで頻繁に発生しており、業務に支障をきたしています。現状の仕様は、分割請求を意図しないシナリオで不整合なデータを生み出し、後続処理でエラーを引き起こすため、改善を強く希望します。

Once a project milestone is created on the contract line details you cannot delete the record.

There should be an ability to delete the milestone if the status = not ready to invoice, so that if a mistake is made, the milestone can be deleted

To Whom it may concern,

I would like to suggest developing a multilingual keyboard.

At present, keyboards (especially mechanical keyboards) are limited to one language setting/layout. For instance, if I would like to purchase a FR keyboard, I would need to buy an AZERTY with all the settings and accents that come with the language. This same keyboard would be suitable to use for English too. However, if I would need to type a text in another language such German, Slavic, Asian or any other linguistic setting else than English or French than I would need to purchase another keyboard.

In order to overcome this, the idea would be to combine physical keyboard + virtual keyboard. The keyboard would be a touchscreen where the user can use keys and shift keys to the language needed like you would usually do on a smartphone.

As a result, you would issue one a unique product and would be more sustainable on the long term.

Many thanks.

Current Business Process Flow looks very muted and not very configurable. Since this is very important and each organization have their own way of addressing these process flows, it will be good if we can make this configurable by the customer IT Admins. Can we make this visually appealing also?