arkadia
2010-08-13 13:46:03 UTC
Sorry to resurrect this old thread, but since the proposed solution was done
for 3.0 in 2005, I wonder if there's a cleaner approach which can be used
with AX 2009?
The proposed solution implies restructuring massively an existing report in
our case, just for sorting on the related table instead of the main table.
Regards,
Eric
for 3.0 in 2005, I wonder if there's a cleaner approach which can be used
with AX 2009?
The proposed solution implies restructuring massively an existing report in
our case, just for sorting on the related table instead of the main table.
Regards,
Eric
I've tried and it works fine!
Many thanks.
Roberto
Many thanks.
Roberto
you're right.
that's not possible in the "normal" way.
but you can use the following "workaround" (available from axapta 3.0)
1st) create a axapta (innerjoinde) view purchline-vendtable (relation
vendaccount-accountnumber),
maybe VW_PurchVend and put in the required fields (all from purchline,
at least accountnumber and name from vendtable)
2nd) create an additional view VW_PurchVend - inventtable (relation
itemid-itemid)
maybe VW_PurchVendItem
put in field ItemName
because the desired combination of vendorname, itemname, purchID isn't
necessarily unique (itemid can be used in more than one purchline for a
certain purchid) you can (if you like) create a 3rd grouping view like
3rd) VW_PurchVendItemGrouped with one datasource VWPurchVendItem and exactly
4 fields
- VendorName
- ItemName
- PurchID
- recID (aggragation count)
now you're able to use this view within your report (or the second if you
need more info)
regards
DouglasT
that's not possible in the "normal" way.
but you can use the following "workaround" (available from axapta 3.0)
1st) create a axapta (innerjoinde) view purchline-vendtable (relation
vendaccount-accountnumber),
maybe VW_PurchVend and put in the required fields (all from purchline,
at least accountnumber and name from vendtable)
2nd) create an additional view VW_PurchVend - inventtable (relation
itemid-itemid)
maybe VW_PurchVendItem
put in field ItemName
because the desired combination of vendorname, itemname, purchID isn't
necessarily unique (itemid can be used in more than one purchline for a
certain purchid) you can (if you like) create a 3rd grouping view like
3rd) VW_PurchVendItemGrouped with one datasource VWPurchVendItem and exactly
4 fields
- VendorName
- ItemName
- PurchID
- recID (aggragation count)
now you're able to use this view within your report (or the second if you
need more info)
regards
DouglasT