Skip to main content
Question

FinPeriod Default Value in Generic Inquiry

  • July 8, 2026
  • 5 replies
  • 60 views

Forum|alt.badge.img+1

Hi all,

I know there is an existing discussion regarding adding @FinPeriodID as the default value for Period schema fields in Generic Inquiries:

Add @FinPeriodID as Default Value for Period schema fields in Generic Inquiry | Community

 

 

 

However, I haven't been able to find the workaround that others have used. Would anyone be able to share some insight?

My goal is to have the Generic Inquiry default to the current financial period, as it currently loads all periods by default, resulting in performance issues and, in some cases, errors.

 

Thanks for your time. 

 

 

5 replies

Forum|alt.badge.img+3

@Crisel As a workaround, could you please try adding the Month Start and Month End as parameters? This may help you achieve a filter that more closely matches the values you are expecting.


Forum|alt.badge.img+1
  • Author
  • Varsity I
  • July 9, 2026

@Crisel As a workaround, could you please try adding the Month Start and Month End as parameters? This may help you achieve a filter that more closely matches the values you are expecting.

Thank you for your reply, @ranjithduraisamy72.

I tried joining the MasterFinPeriod DAC so I could use Month Start and Month End as parameters in the Generic Inquiry conditions. However, I am still encountering the following error:

"System was not able to get record count. Number pages mode is unavailable. Export to Excel is limited to 1000 records."

Has anyone experienced this even after limiting the inquiry by date range? Is there anything else I should check that could be preventing Acumatica from calculating the record count?

 

 


bwhite49
Captain II
Forum|alt.badge.img+12
  • Captain II
  • July 9, 2026

That time out error in GIs is frustrating. Sometimes the only way to get around that is to recreate the GI as a xlsx friendly report in report designer


Forum|alt.badge.img+2
  • Captain I
  • July 10, 2026

Hi ​@Crisel 

I imported your xml into a local environment and did not get the error you are seeing, could be because I don’t have a lot of data in general.

But looking at the GI, it does look like you have a lot of different data sources and joins. Sometimes in accurate joins can create duplicate records which cause record limit issue. I recommend keeping your GI as simple as you can, start with revieing the joins. Removing any unused tables. For example, it looks like you have a relation between InSite and Branch but with no fields linked on, this could potentially cause every result row gets multiplied by the number of branches in the tenant. 

I also like to check my record count by hardcoding a date in the conditions or even in the join directly, to make sure there are no duplicates and the GI returns the number of records I expect to see within that date range. 


Forum|alt.badge.img+1
  • Author
  • Varsity I
  • July 13, 2026

Hi ​@Crisel 

I imported your xml into a local environment and did not get the error you are seeing, could be because I don’t have a lot of data in general.

But looking at the GI, it does look like you have a lot of different data sources and joins. Sometimes in accurate joins can create duplicate records which cause record limit issue. I recommend keeping your GI as simple as you can, start with revieing the joins. Removing any unused tables. For example, it looks like you have a relation between InSite and Branch but with no fields linked on, this could potentially cause every result row gets multiplied by the number of branches in the tenant. 

I also like to check my record count by hardcoding a date in the conditions or even in the join directly, to make sure there are no duplicates and the GI returns the number of records I expect to see within that date range. 

Thank you for this. I was trying to modify the formula; however, I was getting different results, so I did not proceed with that approach.

I will probably try recreating it instead.