BeyondERP.Newsletter
Menu

Job page · Project management and accounting

Import from staging table

A periodic job that imports project actuals from the staging table into integration journal lines, one line per actual. In this system the menu is labelled Project Service Automation, a legacy application; Learn describes the same Import from staging table process for the Project Operations integration journal.

Business process
Manage project delivery
Menu item
action:ProjCDSActualsImportIntegration
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA periodic job that imports project actuals from the staging table into integration journal lines, one line per actual. In this system the menu is labelled Project Service Automation, a legacy application; Learn describes the same Import from staging table process for the Project Operations integration journal.
What you do hereUse it to bring every actual that isn't yet in an integration journal into one, so it can be reviewed and posted. Run it manually or on a schedule.
ExampleBEAT synchronizes actuals every hour. The import job runs every hour at :15; at 10:15 on 11/09/2026 it creates 86 integration journal lines, and 2 expense actuals in GBP are skipped because the EUR-GBP exchange rate for that date is missing.
Import from staging table page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processManage project delivery
Menu pathProject management and accounting › Periodic › Project Service Automation › Import from staging table
Set up firstIntegration parameters Microsoft Learn
Used next byPost all unposted integration journals Microsoft Learn
Related pagesIntegration journal Microsoft Learn
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

When to run it

When to run itAfter each synchronization of actuals into the staging table.
How oftenAs often as actuals are synchronized, usually hourly or daily.
Batch settingsRun as a recurring batch job.
What the output showsIntegration journal lines, one per actual; cost and unbilled sales of time and material actuals are separate lines.

Source: Microsoft Learn

Setup steps on this page

Import actuals into integration journals

Get synchronized actuals ready to post.

Steps from Microsoft

  1. Go to Project management and accounting > Periodic > Project Service Automation > Import from staging table.
  2. Check the period unit for integration journals in the parameters, because it decides whether lines are grouped per day, month, year or all in one journal.
  3. Set it up as a recurring batch job that follows the actuals synchronization.
  4. After each run, read the job log for skipped actuals, for example a missing exchange rate.
  5. Open the integration journal, review the lines (one per actual) and post it.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Run in the backgroundThe dialog has no selection fields; it picks up every actual not yet in an integration journal. Set it up here as a recurring batch job.Checked in Dynamics 365Recurring every hour

Common errors and fixes

MessageWhat to do
Some actuals don't appear in the integration journal.The exchange rate setup is missing for the currency and date; the job log shows an error. Add the rate and run the import again. Microsoft Learn

Test checklist

  1. Count actuals waiting in staging (for example 88).
  2. Run the import.
  3. The integration journal has 86 new lines.
  4. The job log lists the 2 skipped actuals with the missing exchange rate.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Import actuals into integration journalsRecurring batch right after each actuals synchronization, with a daily check of the job log.Actuals missing setup are skipped silently except for the log.How are journals grouped?Deleting unposted lines to get rid of them; they come back at the next import.Test: Import actuals

Feature management and licence

Licence or add-inOn the live system, Project manager, Field Service Integration User, Shop supervisor and Machine operator use this page.

Checked in Dynamics 365

Solution architect

5Design impact

Shared or per companyPer company: lines are created in the integration journals of the legal entity you run it in. Microsoft Learn
Can it be undoneYes, before posting: Lines can be corrected (sales tax groups, financial dimensions) before posting; deleted unposted lines are imported again. Microsoft Learn
If you change it laterCreates integration journal lines. Deleted unposted lines come back at the next import. Project Service Automation itself is legacy (no longer supported since March 31, 2025). Microsoft Learn
Technical architect

6Technical

Menu itemaction:ProjCDSActualsImportIntegration Checked in Dynamics 365
FormDialog Checked in Dynamics 365
Roles to set it up and use itTo use itProject manager ProjProjectManagerField Service Integration User FieldServiceIntegrationUserShop supervisor JmgShopSupervisorMachine operator JmgMachineOperatorGive people one of these roles. On this system, 4 roles can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=action:ProjCDSActualsImportIntegration
Data migrationLoad order: Import from staging table has no data entity in Data management: it is a periodic job and keeps no records of its own. Post or clear the staging table before cutover; new actuals are imported in the target system.Microsoft Learn
Everyone

8Sources