Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

Financial Period in DateInfo Table

There is often a need to find out what Financial Period a Date falls into. This would depend on the structure of the Financial Periods setup in the Financial Year screen.

There is already a Data Access Class called DateInfo which has one row per Date. It would be really cool if a dynamic Financial Period column could be added to this table called FinPeriodID which shows the Financial Period that each date falls into.

  • Tim Rodman
  • Sep 17 2018
  • Gathering Feedback
  • Attach files
  • Tim Rodman commented
    7 Nov, 2018 12:26pm

    Good point about performance. I think your workaround works great, especially because it can be done in a Generic Inquiry without the need for SQL. Thanks Vladimir.

  • Vladimir Panchenko commented
    11 Oct, 2018 09:06am

    You can achieve this with a simple join between DateInfo and FinPeriod Data Access Classes:

    select [DateInfo].*, [FinPeriod].[FinPeriodID] from [DateInfo]
    inner join [FinPeriod] on [DateInfo].[Date] >= [FinPeriod].[StartDate] and [DateInfo].[Date] <= [FinPeriod].[EndDate]

    This solution is applicable to all places where DateInfo DAC is usually used, such as Generic Inquiries, Reports, etc.

    We can consider adding FinPeriodID column in the future, but we'd prefer not to add it because it decreases the performance.