|This feature requires Microsoft 365 when used with Velixo 5, or (experimentally) Excel 2010 or higher when used with Velixo 6 or higher. For prerequisites and an overview of Generic Inquiries, see Introduction to Generic Inquiries.|
The GI function returns the content of a generic inquiry.
This is the syntax for this function:
=GI(Connection, Name, Filter, Select, IncludeHeader)
This function has these Parameters:
|The name of the connection, as specified in the Connection Manager|
|The name of the generic inquiry.|
The conditions that determine which records should be selected from the inquiry.
|Comma-separated list of columns to be included in the resulting dataset. If this parameter is empty, all the columns from the generic inquiry will be returned.|
|TRUE or FALSE, indicating if should column headers be included in the dataset.|
=GI("Demo", "VelixoReportsPro-Projects", A1, "ProjectCD, Description", FALSE)
Description: Returns the project code and the description of records returned by the VelixoReportsPro-Projects generic inquiry, which match the filter conditions specified in cell A1. FALSE as the last parameter specifies that no column headers should be returned.
For configuration details, see Generic Inquiries Options.
Accommodating GI Filters in Acumatica
Acumatica Generic Inquiries can include pre-defined parameters which are used within Acumatica to filter the results of the inquiry:
Acumatica's OData interface (used by Velixo Reports for querying the GI) does not support this type of filtering. To be compatible with your Velixo report, you would need to modify your GI by either (a) removing the parameters or (b) making them optional by ensuring that the conditions in your GI will return the full dataset when the parameters are not specified.
Filtering Large Generic Inquiry Datasets
If you experience long load times for inquiries with a very large result set [e.g. GL transactions or invoices], make sure to always supply a GIFILTER() filter when using the other GI-related functions with such inquiries. Also verify that your inquiry does not involve ODATA functions unsupported by Acumatica [such as startswith() or toupper()]. This will usually allow Velixo Reports to be able to apply your filters on the server [before downloading the data] which can significantly reduce the load time. If, however, the server is unable to apply the specified filter, Velixo Reports will download the entire result set and then apply the filters.