Finance | Project Operations, Human Resources, ...

Project beginning balance limitation to import hours for resources only in the same legal entity

(4) Share

Report

Posted on by hhasbini

In our organization setup, we have shared resources working on projects across the various companies/legal entities.
When planning for migration into D365, we came across a limitation that the project beginning balance form mi=ProjJournalTableBegBal and the data entity ProjBeginningBalanceCostSaleEntity do no allow the import of entries with resources that are external to the legal entity mainly through the condition embedded in the validateResourceInCurrentCompanyOnly() protected member function of the ProjBegBalJournalTrans_CostSales table class.

Are there concrete business reasons for this limitation and are there any side effects if it gets bypassed?

Categories:

Dynamics 365 Finance

I have the same question (0)

All responses (4)

Answers (0)

Adis 6,048 Super User 2025 Season 2 on at

Like (0)

Report

Hi,

Unless someone gives you a straight answer that it doesnt hurt to bypass it, I wouldnt do it.

The way we handled it was to import only sums per category and project. So, if someone needs details, you can look it up and the old system. Usually, after some time, the projects end and with new projects there shouldnt be any issues.

Btw, a very similar behaviour can be found in the pending vendor invoice when it is created from the Intercompany customer invoice. You will find the resource in the pending vendor invoice from another legal entity, however, if you delete it in the field (tab: Project), you wont be able to insert\choose it again. So in case you change something, make sure this process works as well.

My opinion is, try to avoid changing logic in the system, extending yes, but not changing.

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No
hhasbini 24 on at

Like (0)

Report

Thank you @Adis for the response.
The main concern is the logic behind this design.
As there should be no difference between a beginning balance hours summed up entry and a set of beginning balance hours entries per resource.

Was this reply helpful? Yes No
Adis 6,048 Super User 2025 Season 2 on at

Like (0)

Report

Well, I see. Thats not possible in Standard.

I am afraid, you need to customize and test all processes, unless someone comes up who has already done that.

My advice is, dont customize, go with the standard.

Kind regards, Adis

If this helped, please mark it as "Verified" for others facing the same issue

Keep in mind that it is possible to mark more than one answer as verified

Was this reply helpful? Yes No
Suggested answer

Abhilash Warrier 5,402 Super User 2025 Season 2 on at

Like (1)

Report
Hi,

Bypassing the validateResourceInCurrentCompanyOnly() check in D365 to allow external resources in project beginning balances can work technically, but it introduces several potential side effects that you should carefully consider:

Potential Side Effects of Bypassing the Validation
1. Posting and Ledger Integrity Issues

The posting engine expects resources to belong to the same legal entity.

Cross-company resources may cause:

Posting failures.

Incorrect ledger entries.

Misaligned cost/revenue recognition.

2. Project Accounting Discrepancies

Project actuals, forecasts, and committed costs may not reconcile properly.

Resource-based billing or time tracking could fail or misreport.

3. Security and Access Control Risks

Resources from another legal entity may not have proper access rights.

Could expose sensitive data or violate segregation-of-duties policies.

4. Audit and Compliance Concerns

Auditors may flag cross-company entries in beginning balances as non-compliant.

Could violate internal accounting policies or external regulations.

5. Upgrade and Supportability Risks

Customizations that bypass core validations may break during updates.

Microsoft support may not assist with issues caused by unsupported customizations.

6. Workflow and Integration Breakage

Workflows, approvals, and integrations (e.g., with HR or payroll) may assume resource-entity alignment.

Could lead to broken processes or incorrect data synchronization.

Mitigation Tips If You Must Bypass
If you decide to bypass the validation:

Document the customization thoroughly.

Limit its scope to the migration phase only.

Validate all downstream processes (posting, reporting, billing).

Use proxy resources or intercompany setups where possible.

Test extensively in a sandbox environment with real-world scenarios.

If this helped, please mark it as "Verified" for others facing the same issue.
Keep in mind that it is possible to mark more than one answer as verified.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Project beginning balance limitation to import hours for resources only in the same legal entity

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

Project beginning balance limitation to import hours for resources only in the same legal entity

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates