controlling the content of a report table using report attributes

7/30/2019 Controlling the Content of a Report Table Using Report Attributes

1/5


www.ptc.com/cs/cs_27/howto/dwt_attr/dwt_attr.htm

[an error occurred while processing this directive]

Controlling the Content of a Report Table Using Report Attributes

It is often desirable to be able to control what information is listed in a repeat region. Sometimes it isnecessary to display only model information pertaining to the top-level assembly, while at other times modelinformation must be displayed for all levels of the assembly. Both of these scenarios can be achieved bymanipulating the attributes of the repeat region used to generate the table.

For this example, a top-level assembly consisting of several subassemblies and parts is used. The assemblyis displayed in Figure 1, along with a BOM listing of all components by level. Refer to Step 4 for informationon how this table was generated.

In order to accurately describe the top-level assembly, the information in the BOM needs to be displayed in

several different ways:

1. A listing of components in the top-level assembly only (with quantity).

2. A listing of all components, top-level and sub-assembly (with quantity).

3. A listing of all components in order of assembly.

4. A listing of all components by level (with quantity).

5. A listing of the components in unrelated assemblies, where multiple repeat regions are used in the same

table and then 'merged' together.

Figure 1.

Download the Example File for this Technique
http://www.ptc.com/cs/cs_27/howto/dwt_attr/dwt_attr_initial.zip


2/5



Procedure

1. To generate a listing of the components in the top-level assembly only, the attributes of the repeat region

should be set to No Duplicates and Flat. To modify the repeat region attributes, click Table > Repeat

Region > Attributes and select the repeat region. Click the desired attributes, in this example: No

Duplicates and Flat.

No Duplicates will cause each part or subassembly to be listed in the table only once, and will also

display the quantity of each component when the report parameterrpt.qty is used in the table. Settingthis attribute will also cause the components to be listed alphabetically by component name.

Flat will cause the repeat region to only search the top-level assembly for component names.

When these attributes are set, the table will appear as shown in Figure 2.

Figure 2.

2. To generate a listing of all components in the top-level assembly and subassemblies, the attributes of therepeat region should be set to No Duplicates and Recursive.

Recursive will cause the repeat region to search all levels of the assembly (top-level and

subassemblies) for component names.

When these attributes are set, the table will appear as shown in Figure 3.


3/5



Figure 3.

3. To generate a listing of components in order of assembly, the attributes of the repeat region should be setto Duplicates.

Duplicates will cause a component to be listed every time that it is used in the assembly. Use Flat or

Recursive to display information for the top-level assembly only or for all levels of the assembly,

respectively. If the parameterrpt.qty is used in the table, this column will appear empty since every

instance of the component will be listed once per row.

Figure 4 shows the table that will be generated when Duplicates and Recursive are set. Note that ifRecursive is set, the first component listed is the top-level assembly itself. The top-level assembly can be

removed from the BOM using a filter if it is not required to be listed.For more information on using report filters, refer to the Suggested Technique for Using Report Filters
http://www.ptc.com/cs/cs_27/howto/dwt_filt/dwt_filt.htm


4/5



Figure 4.

4. To generate a listing of all components by level, the attributes of the repeat region should be set to NoDup/Level and Recursive.

No Dup/Level will cause each component to be listed only once per level in the table. For example, if

part is used in two different subassemblies, it will be listed twice in the table. If the part is used in the

same subassembly twice, it will appear as one row in the table with a quantity of two.

Indentation can be applied to a repeat region that has Recursive specified as one of its attributes. T

add indentation click Table > Repeat Region > Indentation and select the leading cell of the column

where indentation is to be applied. Enter a numerical value to define the amount of indentation. Click


5/5



Update Tables to see the result.

Figure 5. Illustrates the resulting table when the No Dup/Level attribute is used with Indentation. Note thathe part TRIANGLE_2 is listed twice in the table. This is because the part is used in both the H_PLATE andV_PLATE subassemblies.

Figure 5.

5. Sometimes it is necessary to show some subassemblies recursively and others flat, all in the same repeatregion. This can be accomplished using Table > Repeat Region > Flat/Rec Item. Select the table regionfollowed by the item to make either recursive or flat. If the attributes of the table are set to Flat, selected itemwill be made recursive. Conversely, if the attributes of the table are set to Recursive, selected items willbecome flat. Click OK > Done/Return after selecting the desired items.

6. Start Index can be used to 'merge' the BOMs of unrelated assemblies when multiple repeat regions arecreated in a single table. Merging the regions will ensure that the index numbers of the two regions areconsecutive instead of being duplicated. This is only relevant when the parameterrpt.index is used in therepeat region. To merge the regions, click Table > Repeat Region > Attributes and select the regionwhose index numbers are to be changed. Click Start Index and select the region that the index numbers wilcontinue from. No Start Idx can be used to separate merged regions.

Download the Finished File for this Technique

COPYRIGHT 2013, PTC Inc.
http://www.ptc.com/common/ptccopy.htmhttp://www.ptc.com/cs/cs_27/howto/dwt_attr/dwt_attr_final.zip

controlling the content of a report table using report attributes

Documents