Skip to main content

I have a GI that queries a custom SQL View using a custom DAC. This GI has parameters StartDate and EndDate. Both of these parameters are not required and neither have a Default Value.

GI Parameters

I am then using the StartDate and EndDate to filter the results base on the OrderDate as seen here:

GI Conditions

However, when I run view the inquiry, every time I try to select a date in one of the date parameters, it automatically gets cleared out to nothing - thus making the GI useless.

 

I’ve tried making the parameter dates Default to @Today, but when the inquiry is run, whenever I try to change the date, it automatically reverts back to the default.

 

22R2 Build 22.213.0010

 

TIA, Dave

@davidrichards12  Can you please attach your GI here? 


Here is the exported GI


@davidrichards12  I don’t see any issue with the GI configuration, as you built this GI based on the SQL View, I could not able to see the output of this GI.

Possible to share the customization package or SQL View? 


Here’s the SQL View


@davidrichards12  Thanks for providing the SQL VIEW.

I created the SQL VIEW in my local machine and created a DAC and GI is working fine with the parameters and able to filter the details.

Please find the screenshot for reference.

 


Thank you for looking into it.

I don’t know if there is something wrong with my machine or my installation that is causing this then. Most bizarre.


Something to note is that you haven’t included CompanyID in any of your joins and you haven’t included a CompanyID column in the fields that the view is displaying.


@davidrichards12  Have you tried by clearing the browser caches or tried in a different browser and observed the same issue?


@davidrichards12  As per Django's suggestion, please include 'COMPANYID' in the SELECT statement, so that in GI it will fetch the right tenant data. 

Although this is not related to the issue that you are facing.


@Naveen Boga I almost exclusively use Firefox. But to test, I tried it in Chrome -- and I saw the same behavior.


@davidrichards12  Please create a new GI (Copy and paste the same) and check once and confirm


Reply