Is it possible to have grouping on custom tabs similar to addresses and others on different tabs of an account?
Yes! This is possible to do...
This was what I was told back in beta (so I'd look through the docs to make sure it hasn't changed significantly)
In TR_CUSTOM_TAB you’ll see a column called grouped d_object. If you have a grouped version of your datawindow (you have to design it) then you can put it here. Then you’ll get a Group by Constituent checkbox at the bottom.
There are sample custom screens in the sample PBL that came with the release.
HTH,
Heather
I've been looking at the sample screens. Anyone know if there is new documentation to go along with this?
I guess I should ask this - what should my dataset look like for the grouped screen? Should I have another column for affiliated customer number?
I know there is a new Custom Report doc pending; I bet that will cover this sort of thing, too.
Just created a grouped custom screen here by copying infomaker object 'ld_sample_custom_volunteer_grouped' from the v11 SampleCustomScreens pbl.
More info see:
http://www.tessituranetwork.com/~/media/Documentation/Customizations/Custom_Tabs.ashx
and
http://www.tessituranetwork.com/Help_System/Content/System_Tables/TR_CUSTOM_TAB.htm
Note, In Infomaker you have to copy the formula for Font Size and Bold for the 'customer_no' field with the AffiliateDropdown tag. (in the group heading).
I left the 'Grouped D object' column in TR_CUSTOM_TAB blank and put the name of the grouped object in the 'D object' column so its always grouped. This is just as we prefer the grouped view and don't want to have to maintain two infomaker screens.
Do you use just one sproc for the grouped and ungrouped IM objects? Or did you need to build a new one? What do you do with the affiliated customer_no?
By the way, I have no idea what this means.
"Mid(LookupDisplay(customer_no), 201)"
But it seems relevant. I am going to paste that into every available text box in InfoMaker today and see what happens.
I used a query in the infomaker object rather than a SP. Didn't do anything special with the affiliated customer_no except copy how it worked in the sample:
My query is as follows and works fine on household records:
SELECT a.customer_no,
a.allowemail_flag,
a.allowmail_flag,
a.allowphone_flag,
a.allowsms_flag,
a.allowshare_flag,
a.asked_dt,
a.id_key,
CreateLocation = a.create_loc,
CreatedBy = a.created_by,
CreatedDateTime = a.create_dt,
UpdatedBy = a.last_updated_by,
UpdatedDateTime = a.last_update_dt
FROM LT_PRIVACY_ACT a
Where (a.customer_no in
(Select expanded_customer_no From V_CUSTOMER_WITH_PRIMARY_AFFILIATES Where customer_no = :constituentid))
Hope that helps.
Thanks Dara - this helps! I think I've got it worked out now!
Looking at the bold box for customer_no - the sample has this expression:
If(customer_no = currentconstituentid, 700, 400)
How do I get currentconstituentid? It doesn't seem to be part of the select they're using in the data source...
How it works in the samples (and you can do the same thing) is that currentconstituentid is a computed column object with the visible property turned off. The compute expression doesn't matter (in the sample it's just 0) and when the datawindow loads we automatically look for a computed column with that name and replace the expression with the id of the current constituent.
Unknown said: By the way, I have no idea what this means. "Mid(LookupDisplay(customer_no), 201)" But it seems relevant. I am going to paste that into every available text box in InfoMaker today and see what happens.
A little confusing, eh? This expression returns the row number of the constituent as it appears in the constituent navigator (we append the number of the row to the name of the constituent that appears in the customer_no dropdown datawindow after 200 characters). It gets used as the secondary sort criteria after putting the currently selected constituent first. We may change this in the future to use an extra column and work more like currentconstituentid, but for the moment, this is the way most of our screens work and the way to get the right sort order in custom screens.