I installed the Gridview upgrade 9.0D (110828)and lost most of the fields on my Commission Report. I'm using the composite table *SR Trans w AR, OE Hst Head, IC.

Hopefully I can get everything back one way or another but I'm just wondering if we're suppose to keep using the composite tables now that you can "insert related column"?

"most of the fields" ..

Were the fields from Sales Analysis, AR Master, OE History Header or IC that were lost?

I can think of no reason for this to have happened unless you had a "custom" @Z dictionary and it was over written by the GV 9.0D install and that @Z dictionary did not have the same "links" defined.

Whenever possible the "Insert Related Column" is the way to go.

Michael:

Are all the composite tables name @Z or only the custom ones? After installing GV 9.0D I cannot print many of the views that use composite tables (I haven't test them all). I had to go back to older versions and recover the @Z files to be able to run some of my views again. I will need to recover the customized ones as well.

The current Adagio {Composite Table 9.?} have composite tables that cross applications, SR Transactions to I/C Items for example. Composite tables for the same application are now found in the application dictionary, AR Transactions to AR Customers will be in the Adagio Receivables 9.0? dictionary.

The older Adagio {Composite Table 8.?} dictionary had composites that crossed applications as well as composites for the same application, A/R Transactions to A/R Customer for example.

Softrak will no longer be maintaining Adagio {Composite Table} dictionaries and you are encouraged to use the "Insert Related Data" capability of GridView when creating/maintaining your Views.

Hi Michael,

OEBillName was replaced by OEHEADCust Disc Level
OEHeadComment2 was replaced by Comment1
Document # was replaced by Doc Type
Standard Cost was replaced by Pick Sequence

Good thing pay day is next week. I'll try to fix or re-create the whole report.

Definetly caused by a difference in the Adagio Composite dictionary. Depending on the version, a field labelled {Name} is at the bottom of the A/R Customer Master table in the Composite Dictionary. Looks to me like that field was there when you created the View but it is not there in your currently installed dictionary.

Unfortunately I don't know much (anything) about dictionaries.. however, so far it looks successful with a new view using OE Hist Detail w/Header for all the fields I need plus inserting a related column from IC Items 1/3 Master to get the standard cost. It's looking good!

All the fields I want are there now but the problem is that it takes 40 minutes to load. It's counting one by one through 684,000 records. What am I doing wrong? HELP.

I recreated the view using Composite Table 9.0B\*SR Trans w AR, OE Hst Head, IC and it loads in 3 minutes vs 45 minutes using OrderEntry 8.0A-8.1C\OE Hist Detail /w Header. When I remove the references to related column {category} from the filter, it loads in about 3 minutes instead of 45 minutes. I need to filter by {category}, however, so I guess I'll use the composite table since it doesn't slow it down when filtering by {category}.

Another problem I'm having that I can't figure out is with this filter:

AND (
{Date} >= QUERYDATE("Enter START Date:", TODAY()),
{Date} <= QUERYDATE("Enter END Date:", TODAY()),
Left({Salesperson},5) =Left(QueryString("Enter LINDSY, KINGSN, LONDON", ""),5),
{Qty} <> 0,
{Amt} <> 0,
{Category} <> " BE",
{Category} <> " MC ",
{Category} <> "RCO",
{Category} <> "RCA",
{Category} <> " SH",
{Category} <> " ZZ",
{Item #} <> "Tax0",
{Item #} <> "Tax1",
{Item #} <> "Tax2",
{Item #} <> "Tax3",
{Item #} <> "Tax4",
{Item #} <> "MIS1",
{Item #} <> "MIS2",
{Item #} <> "MIS3",
{Item #} <> "MIS4",
{Item #} <> "MIS5",
{Item #} <> "MIS6"
)

For some reason, when we enter the start date, end date and salesperson, the view loads but immediately pops up and asks for the start date, end date and salesperson AGAIN. After the second round, it loads correctly. Any idea how I can stop it from asking the 2nd time for the start date, end date and salesperson?

Hi Susan,

The repeating of the Query prompts when starting is a bug that was recently introduced when the 'Refresh on open' option is set on the view. This will be fixed. If you disable this option and just press F9 after opening the view, you will only be prompted once for the Query values.

As for the slowness depending on one table versus another, it like has to do with indexing and typically the category code does not have an index, thus every record has to be read in order to determine if the filter criteria is met.