{"id":28001,"date":"2017-06-16T14:16:54","date_gmt":"2017-06-16T06:16:54","guid":{"rendered":"http:\/\/localhost\/help\/?page_id=28001"},"modified":"2024-01-17T10:47:59","modified_gmt":"2024-01-17T02:47:59","slug":"ddcount","status":"publish","type":"page","link":"https:\/\/oihelp.corporate.ifs.com\/help\/p2-server\/calculations\/ddcount\/","title":{"rendered":"DDCount()"},"content":{"rendered":"\n

Format<\/h2>\n

DDCount(InputValues)<\/strong><\/p>\n

Returns<\/h2>\n

Counts of the input values for each timestamp.
\nTypically this function is used on the return value of a DDGet() or DDGetAttributes() call since these functions can return multiple values for a single timestamp (by fetching the attribute of several entities).<\/p>\n

It is possible to retrieve very large volumes of data through indiscriminate use of this function. Retrieving large amounts of Historian data across a slow network can affect system performance for all users of the system.<\/p>\n

Inputs<\/h2>\n

InputValues:<\/strong> A collection of values where each value contains the necessary metadata (see Useful to Know<\/a> below) which indicates the name of the source entity (DDGet<\/a>() and DDGetAttributes<\/a>() can produce such return values).
\nBehaviour: Required
\nDimensions: MultiCollection
\nValid data types: Decimal, Integer<\/p>\n

How to format data types<\/a><\/p>\n

Useful to Know<\/span><\/h2>\n

In the calculation engine, values returned by DD() functions have metadata assigned to them, such as entity name and start\/end times. Other DD() functions can use this metadata to assign additional information to values they receive. In this way, the metadata is used by nested DD() functions to reduce complexity but increase versatility. Which metadata is used and how it is used is specific to each function, and is described in the Input Values section above, where applicable.<\/p>\n

Examples<\/h2>\n

Expression: DDCount(DDGetAttributes(DDGetEntities(\"myHierarchy\", 2, \"rootEntity\"), \":myAttribute\"))<\/span>
\nDescription: This expression produces a similar result to \"Count({childEntity1:myAttribute}, {childEntity2:myAttribute},... {childEntityN:myAttribute})\". However, DDCount() will dynamically search the hierarchy, meaning that if you add or remove wells from the hierarchy, that will automatically be taken into account in the calculation. \u00a0
\nResult: Returns the count of all fetched values of \"myAttribute\" for each child entity maximum 2 levels below the \"rootEntity\" in \"myHierarchy\".<\/p>\n

Tip: If you have access to the sample data, try running the following examples using the calculation tester<\/a>.\u00a0<\/p>\n

Expression: DDCount({SampleDDGet})<\/span>
\nReturns: The count of all fetched values in the SampleDDGet calculation tag. This tag is actually the same as the DDGet() function in the below example.
\nResult: 9<\/span><\/p>\n

Expression: DDCount(DDGet(\"P2 Corporate\", 5, \"Western Australia\", \":Oil Production\", \"{[Oil Producing Well]:Status} == 0\", \"Oil Producing Well\"))<\/span>
\nReturns: The count of any Oil Producing Wells that are Online, and in the state, Western Australia.
\nHow it works: The function\u00a0scans through the P2 Corporate<\/em> hierarchy, starting at the node Western Australia<\/em>, and then starts searching down the hierarchy, to a limit of 5 levels deep. When searching, it looks for any entities that have the template Oil Producing Well<\/em>.\u00a0 For each of these entities, it then gets the data from the Oil Production<\/em>\u00a0attribute, but will only return this data if the Status<\/em> attribute returns a 0 (i.e. the well is ONLINE). Once it has all of this (from the DDGet function), it then counts the number of values that were returned, to give a count of the wells that are Online that have any Oil Production data defined.
\nResult: 9<\/span><\/p>\n

Release History<\/span><\/h2>\n