web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics 365 | Integration, Dataverse... / Gettubg Closing (Perio...
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

Gettubg Closing (Period 13) Transactions via API

(2) ShareShare
ReportReport
Posted on by JH-02041856-0 4
I am unable to see Period 0 (opening) or 13 (closing) entries using the GeneralLedgerActivities endpoint (entity) in Dynamics 365 Finance. Any ideas how to troubleshoot this? Or is there a different endpoint I can use for these closing/opening  entries?
Categories:
Dynamics 365 general
I have the same question (0)
  • Suggested answer
    Holly Huffman Profile Picture
    Holly Huffman 6,554 Super User 2026 Season 1 on at
    Good morning, afternoon, or evening - depending on your location :)
    Hope you are well today!
     
    Here’s how you can approach this issue --
    1. Verify Posting Layer Filters: The GeneralLedgerActivities entity typically filters data based on the posting layer (e.g., current, opening, or closing). Ensure the API request specifies the correct posting layer to include Period 0 (opening) and Period 13 (closing) entries.
    2. Period Allocation Check: Confirm that the transactions for Period 0 and Period 13 were correctly allocated in the system. If they weren't posted correctly, they won't appear in the API results.
    3. Explore Alternative Endpoints:
      • Consider using the GeneralJournalAccountEntry entity, as it often provides more granular data, including all types of journal entries.
      • You might also examine the LedgerJournal or GLTransactionLine entities if additional journal data is required.
    4. Inspect Financial Dimensions Configuration: Transactions in these periods could be filtered out due to financial dimensions setup in the request. Double-check the dimensions applied to ensure no filtering excludes opening/closing entries.
    5. Debugging the API Query: Test the API call using the data management workspace in Dynamics 365 Finance. It can help identify whether the issue lies in the entity itself or in the query parameters being sent.
    6. Review Period Setup: Ensure that Period 0 and Period 13 are properly defined and active in the fiscal calendar. If there’s an issue in how they’re configured, they might not be accessible via the API.
     
     
    Hope this helps :)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 122

#2
CP04-islander Profile Picture

CP04-islander 57

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 57 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Welcome to the Microsoft Dynamics 365 forum!
Identifying an Org as CDS or Dynamics
Get batch job history log from D365 FO to Power Automate
Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans