| Table of Contents | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Overview
The Publish Filter provides the ability to narrow the list of devices and meters that a given publisher will use. This is helpful if you want a certain publisher to only publish a specific type of device, or only those in a specific folder.
| Info |
|---|
See the General Object Configuration guide for assistance configuring the General tab. |
...
Click the Edit Group button to configure the Publish Filter Record Collection of rules to apply to the filter.
Records
| Info | ||
|---|---|---|
| ||
Clicking the "Tabular Display" button will open the filters in a grid and will make adding and editing multiple rules simpler. All examples shown below use the Tabular Display. |
Records can be added or removed using the Add, Remove and Copy buttons on the lower left. Each record uses the following fields:
- Aggregate. Aggregate option to combine current filter with next filter that is added. When the aggregate is blank and the following row also has a blank aggregate, it acts as an OR next filter. The Example section of this document explains the results of each. The available options are:
- "AND all previous filters": This aggregate groups the current row with all the rows above it, then "ANDs" that group with the following
- "AND next filter": This aggregate "ANDs" this filter row with the one immediately below it.
- "OR all previous filters": This aggregate groups the current row with all the rows above it, then "ORs" that group with the following
- "OR next filter": This aggregate is used to separate other filter rows that are joined by any of the above three (* This is the aggregate used when the "aggregate" value is left blank.)
- Name Text. Text used to query for object's name. Can include wild cards ? (to represent a single character) and * (to represent any number of characters).
- Not Name Text. Text used to exclude objects. Can include wild cards ? (to represent a single character) and * (to represent any number of characters).
- Parent Folder. The folder containing objects to publish. Child folders are included. Note: the use of "Unassigned" tells ACM to look in every folder.
- RecordId. Display Name of Record.
...
| title | Saving Record Collection Changes |
|---|
...
*After closing the Record Collection form, save the object to save any changes made to the record collection.
Aggregate Examples
More information about the use of each aggregate and the order of operations are found on the Publish Filter Aggregate Examples page.
Filter Examples
All examples will use the tree below and displayed in the "Tabular Display" view. These examples show the solution requiring the least number of aggregates.
...
| Info |
|---|
| One of the common challenges in building filters is how we think about what we want published and our use of the "AND" and "OR" words. For instance: "I want every device in Device Set A and Device Set B" entered as a filter would actually be processed as "I want every device that exists in both Device Set A and Device Set B". Instead we need to think of it as "I want every device that exists in Device Set A OR exists in Device Set B." |
Example 1: Publish data for every device that
...
begins with 'NGCTT' in Device Set D or is in Device Set A.
What works:
Using the "OR next filter" aggregate and an ‘*’ after ‘NGTT’ so ACM knows
to look in both folders, and a '*' after NGCTT so it searches for anything that starts with NGCTT, regardless the number of characters afterwardsthat objects to publish are:
- Found in the Device Set A folder OR
- Begin with ‘NGCTT’ and are found in Device Set D folder.
Example 2: Publish data for every device that
...
exists in Device Set D
...
and does not start with 'NGCTT' or exists in Device Set A.
What works:
- In this case, the filter is the same as example one Example 1 except the NGCTT* has moved into the "Not Name Text" field so that ACM rules it out.
...
In ACM, it is not possible to rule out an entire folder. Instead, we need to rule in all acceptable folders.
What works:
- Using the "OR next filter" aggregate to include each folder.
Example 4: Publish data for all devices that have both an "m" and a "y" OR are in Device Set A
Here we used What works:
- "AND next filter" on the first row to find devices containing both an "m" and a "y"
...
- and on the third row, we use the "OR all previous filters" to mean that all of the previous filters must be considered as one.
- "AND next filter" on the first row to find devices containing both an "m" and a "y", an "OR next filter" on the second row and no aggregate on the third row would have the same results
Example 5: Publish data for all devices that have both an "m" and a "y" but do NOT have a "p"
What works:
- Here we needed to "AND next filter" all three.
What doesn't work:
- Had we used "OR next filter before the record with the "
...
- p", it would have returned devices containing an "m" and a "y" and ALSO all devices that do not contain a "p" (whether or not they contain an "m" and a "y")