TIMSS 6: Base Crystal Report Naming

There are a ton of Crystal Reports that come with TIMSS 6. Several of them are similar and are classified/named in a particular fashion.

This first distinctions are for Trade Associations and Professional Societies. Trade Association version will have a C after the report number (for company), whereas reports for Professional Societies will have a P. C reports will focused on companies, and P reports will focus on individuals. Both will be sorted/grouped appropriately.

The second distinctions are for Internal (I) and External (E) version of the report. Internal versions are meant for internal use only. External versions are for distribution outside of your association and not all customer data is to be shared outside. Thus the external version should check the Publish flag on communications (i.e. phone/email) and the Confidential flag on addresses:

CUS_COMMUNICATION.PUBLISH_FLAG='Y'

CUS_ADDRESS_DETAIL.CONFIDENTIAL_FLAG='N'

In general, reports for orders are considered internal and directories are external.

Applies to: TIMSS6

TIMSS 6: More Ad-Hoc Query Security

It was pointed out to me that there is another way to add security to Ad-Hoc Queries. On the META001 screen where one sets up views for use with ad-hoc queries, there is an Available for Public check box. If you un-check this box, the Special Security button is activated, and you can select groups that can use this view for queries.

When a user goes to Ad-Hoc Queries they will only see queries that use views that they have access too. This is different from my previous post that puts security on the reporting category in Ad-Hoc Queries.

Applies to: TIMSS6

TIMSS 6: The Magic of CUS500

The CUS500 TRS report can be used to print a variety of labels. In System Types & Codes, there is a type for LABEL_FORMAT with codes corresponding to the various labels available. These correspond to Crystal Reports on your TRS. So if you run the report with the AVERY5160 label format parameter, the process will run the CUSLABEL_AVERY5160.rpt report on your TRS. If you don't like the layout of the labels or the font, that's the report you'd update.

And if you wanted to add a new label format for name badges or tent cards, just add the appropriate code and the corresponding Crystal Report to your TRS.

You can also pull all kinds of data into this report. It is based on the CUS500_VW so you can use the filter on the Advanced Job Parameters tab to select any customers you want: in a given state, or participants in a meeting, or committee members (the latter two would have an exists in the filter query and can have addresses other than their primary; see below).

There are 3 parameters for this report: Label Format- the layout of the report from code described above; Sort Order- to sort the report based on a field; Select Primary Address Only- Y for only their primary address, N to print all their addresses (for committee or ship to addresses other than primary, you'd choose N and then filter with exists to select the correct address).

You will probably want to have 2 runs for your labels: one that pulls GOOD addresses, and one that pulls BAD address so you can see who won't be getting your mailing.

Applies to: TIMSS6

TIMSS 6: Add Application Parameters

Have you created any custom processes that could use a system wide parameter? If so you can add it to the Application Parameters and have your process look up the value.

Just pull up the screen (APP008) and hit the plus to add a parameter. You probobaly want to put it under the USR-User Defined Subsystem so TMAR knows it's yours.

This data is kept in the APP_PARAMETER table. So in your process, query that table for the value of your parameter. This will allow users to change the parameter (if you give them permission) without re-writing your process, plus you can re-use the parameter in other processes.

Applies to: TIMSS6 & Personify