CoDeSys Visualization Dropdown Menu Custom Values in modelTextList - plc

Using CoDeSys, I have a drop down list for a visualization that uses an enumeration of values for the options in the list. The enumeration comes from a separate library and for my particular application I would like to use only a subset of the enumerated values in the drop-down. So in order to accomplish this, I have a text list containing only two values, 5 and 7.
This seems easy enough but when I go to run this particular drop-down I see the two values correctly but I also see numbers up to 12 for the missing IDs. 12 is weird since the enumeration has 22 enumerated values.
Is it possible to have only the two values show in the drop-down without making the ID's 0 and 1? I would really like to use the library enumeration.

It turns out there is a checkbox that must be checked called "Filter Missing Textentries" so that the drop-down list to only contains the values given in the text list. Once that box is checked it will remove the random numbered values.

Related

Remove Values from Grafana

I have a scenario like this pic, where I get the status from my hosts.
I have a few dozens of hosts so I would like to apply some filters, like showing only hosts that had problems during certain period.
I found one option, that I used in this example, that is the remove[below/above]value, but it only removes the value itself, not the entire column, the host itself.
Basically, considering this example, I would like this host(second bottom-up), that didn't have 1 value during this last week, did not appear on this screen.
Is there a way? I hope the question isn't very confusing.
The removeBelowValues function removes the values from the serie, but can't remove the serie.
Depending on your data, you can turn the series to rows, then remove rows using "Filter Data by Values" transformation. See https://grafana.com/docs/grafana/latest/panels-visualizations/query-transform-data/transform-data/#filter-data-by-value
Example:

How do I group dates in IBM COGNOS when building a front end dashboard

I am an extreme newbie to COGNOS (5 days give or take a few hrs) and have been thrown in the deep end.
I have a data package i am working with and the only date field I can use has the property of timestamp. I have looked through other questions that are similar and i have used the "CAST" function to turn the field into a date so this has worked.
cast ( [TR_Logical Layer].[Fact Event].[Period Datetime],DATE) - so I was happy with that.
However now when I am building the graph, I am getting repeated dates - and I can only think that this is because somehow it is still holding onto the timestamp portion of the field.
Please how can i get all of my many dates for say the 21st Jul to be one?
Possible issue: Repeating is probably due to how it is grouped (down to the time which would have the day repeating)
Suggested solution: Add a determinant to control granularity and grouping
Here are the steps
https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=determinants-specifying
Click the query subject you want, and click Actions, Edit Definition.
Click the Determinants tab.
Click Add under the Determinants box.
The entry New Determinant displays in the box. To give this entry a meaningful name, right-click it, and click Rename.
To define a key, right-click a query item in the Available items box and click Add as Key. Tip: You can also drag query items to the Key box.
To identify which query items should be associated with this determinant, right-click query items in the Available items box, and click Add as Attributes.
Tip: You can also drag query items to the Attributes box.
You can have a determinant with no attributes defined for it. Framework Manager uses this type of determinant to indicate which query items are indexed.
To specify that the selected determinant should be used as the unique identifier, select the Uniquely Identified check box.
Do this only if the data in this item is unique for every row in the underlying data source. You can specify more than one unique determinant if they are truly unique. At query time, the relationship being used will determine which unique determinant to use.
Select the Group By check box to indicate that when keys or attributes associated with that determinant are repeated in the data, IBM® Cognos® Analytics should apply aggregate functions and grouping to avoid double-counting.
If you want to change the order of the determinants, use the arrow buttons.
Determinants are processed in the order in which they are specified in the model.
Click OK

Creating a combined option in dimension

I have a dimension which is simply a list of user groups such as the below:
User Type
Type A
Type B
Type C
I am currently visualising these as an individual pie for each user type with the numerical value shown in the middle which is their answer to a question from another measure. However, I'd like to create a fourth type which is 'All users' so that I have four pies showing at once: All Users, Type A, Type B and Type C.
Is this possible? Would it be a calculated field? I have tried groups but can't get it to work.
Any help much appreciated!
Assuming for the moment that you have User Type on the Columns shelf, you can simply choose Totals->Show Row Grand Totals from the Analysis menu.
An alternate approach is to display two worksheets on the same dashboard. To do that, simply duplicate your worksheet. Remove User Type from the view in the new worksheet. And then place both views next to each other on a dashboard, possibly in a layout container to keep them lined up nicely. Format a bit to remove the titles and outside borders and they can look like one unit.
Remember what a dimension does. It partitions the data rows according to the value of the dimension field, assigning each data row to exactly one partition - exactly like a Group By clause does in SQL. So a data record can’t be associated with more than one member of a dimension. Totals behave differently, which is why they address your use case.

Tableau Filter from calculated field, but I want to exclude some

I am trying to add to my current calculated field.
It is a fairly simple LEFT(UPPER([STR]),2) that I am currently using. This populates a filter list. However, I want to either modify the formula or the list itself to only include [STR] items where underlying data is and for any that do not have data, they are left off the list until they have data to be selecting.
think of the STR as if it were states abbreviations. IF COUNT([Things]) = 0 then I don't want the state on my filter list, but if there is or if there later gets some Things added in that state I want it to show up.
I tried using IF COUNT([Things]) > 0 THEN LEFT(UPPER([STR]),2) END but that doesn't seem to work. I am also open to just using a condition for showing the filter if that can work, but I am not sure how to set that up.
Strangely I had tried this solution before. I choose Show only relevant values on the filter in the filters box, that made it show nothing at all. However, if you click the drop down arrow on the Show filter card and choose show only relevant values that works.

Filemaker 13 Pro - Trying to create button labels from field entries

I am trying to create dynamic buttons using the entries made in a field. I have a field called shows that contains show names. I want the button labels to reflect those names.
I have looked at using text fields as the labels and Set Field, but I cannot make a loop work to get the names.
Any help or direction is appreciated.
Thanks
It looks like you are trying to do something complicated where you do not need it.
I think, you have a field where you have a list of entries separated by carriage returns and you want every entry to appear as a label on a button.
In FileMaker 13 the default button label can not be calculated, so you will need to create buttons without labels and create and place the labels on top of them.
You will have to set labels to Insert/Merge.. and decide if you use calculated fields or global variables. You will need extra fields for calculating stored labels or you will need to populate your variables through the script.
To get the list item you can use GetValue() with a list (your field) and item number (starts at 1) as parameters.
As Michael mentioned, to make it dynamic you will have to use a portal, you are better off storing your labels as separate records.