We have a device template with an interface definition that contains a capability with Enum as schema... with possible values 0, 1, 2. For each of the values, I've defined a display name as shown in the image here.
I've expected this display names would show in the Dashboard when showing "Last known value", however it still shows the values (0, 1, 2).
Am I missing anything here? Where/how are these enum display names used? How do we use them on the dashboards?
The following screen snippet shows an example of the mapping enum values of the telemetry state in the IoT Central preview app:
Last known Value, where is displayed raw value (no mapping) from the telemetry data
State History, where is used mapping to the DisplayName during the time range. Note, that if the mapping is out of the enum values, the DisplayName is empty.
Pie chart, where is displayed the counts of the same values during the time range
I have checked my configuration and I work in the Interface with the Enum schema too.
IoT Central Interface + Schema view
But I also have set on the Customization section for the Device Template the Semantic type State.
IoT Central - Customize Interface value
In this Case I got the "Last known value" graph with the text.
The State History I got only when the capability type is set to State by the semantic type allready ;)
IoT Central - Capability type "Sate"
Related
I have attribute priority which is enum type in CsTicket type and my requirement is to show the different images of low high and medium with the status of the ticket like arrow .
Can anyone suggest how I can do it .
Expecting the arrow to appear based upon the selection of status.
As I build custom entry screens for our business requirements, an objective is to utilize generic inquiries as the entry point for a consistent user experience with the rest of the system. I have 3 user entry screens, each of which is on the Site Map in the same place. Two of the GI's allow me to select the Site Map node for these user screens and assign the Entry Point to display the GI instead of the user entry screen. One does not. All of them appear to have very similar DAC structure as well as Graph structure including naming the primary graph in the DAC.
What causes the site map node to be available (or not) for assignment of the GI as an entry point. (For instance, is there an orphaned record I might seek out in SQL from deleting a previous attempt?)
I am on Acumatica ERP 2018R1 (Build 18.113.0018).
There were a couple of issues that prevented the Generic Inquiry from allowing it to be set as an Entry Point. If you have this same issue, review the related DAC's carefully for errors that may not be compile time issues. Also, double check all of the definition tabs in the generic inquiry for fields that you renamed or dropped but failed to adjust in the GI. In my case, the last issue resolved that allowed the GI to be turned into an entry screen was a poorly defined parameter.
To troubleshoot, try making the GI very simple. If you cannot reach the screen to select as the entry point and the GI is very basic, odds are that you have a problem somewhere in the DAC. In some of the DAC's for screens that I could not setup as an entry point, I had reference to a setup DAC that was not using Currrent when it should. This small error in the DAC was the problem on 2 of my 3 screens.
In my case, the primary view name in the graph was not 100% the same as the datamember on the screen. One was camelcase and the other pascal case. Make sure the view name on both the screen and the graph is exactly the same.
I have to integrate GA in project which uses a multi parameter search which should be tracked in detail.
Imagine a web shop selling computers with the following choices (some of them are even multi-selects):
RAM size
Type of computer (e.g. laptop)
Color
...
Using the Site-Search option in GA in conjunction with virtual pageviews it caught my eye that there is a restriction, that you can only define 5 parameters. This seems to me being a standard scenario but google search doesn't help me finding an answer.
How would you implement/configure a multi search scenario like this in GA?
You could set up a hit-scoped custom dimension for each parameter (RAM, Type, Colour etc.). Then, when the search results are shown, you would push something like the following to the Google Tag Manager dataLayer:
dataLayer.push({'ram_size' : '8gb', 'type' : 'Laptop', 'Colour' : 'Grey'});
Then in GTM, you would need to set up a variable for each one of these and pass those variables to the GA page view tag in the custom dimensions section of the tag configuration.
A client of mine has 2 web applications, sharing the same content types.
These content types (let's call them "A") are of a base type DocumentSet, and include a Managed Metadata Property "B" (which is a indexed column on WebApp 2 in all libraries).
There's one strange thing going on however. Searching and indexing works fine. But when we search in WebApp 2, it always shows the value of the Managed Metadata Property field "B" in the description. And it's always the wrong one. Whatever the real value is of property B in that documentset, it always shows a certain other value from the taxonomy store.
I tried inspecting every single property and field of the item in Powershell, but could not find any reference to the displayed property value.
My question in this matter is:
1) How on earth could this value be crawled and included in the description if it does not exist in the list item?
2) How can I inspect the crawl database to check what properties it has stored?
I am building a phone catalog of my organization (an AJAX application which accesses the search.asmx web service).
I'd like to show a list box where the user could select a department (which is stored in managed property Department). To fill the list box with values, I need to somehow select all the distinct values of that property.
Is it possible through search.asmx web service?
What I've found:
an article, which states that it is possible, but it does not use the web service interface
a Microsoft's white paper which states that "If the protocol client specifies at least one property, it MUST also specify the Path property. If it does not, the protocol server MUST return the status code "ERROR_BAD_QUERY"."
The two findings are somewhat inconsistent. (and, yes the search really returns ERROR_BAD_QUERY).
Why bother to check with the web service or complicate it?
Get all the properties into a DataTable.
Then create a DataView & then you can apply the DISTINCT on required column.
Finally use it to bind to your list box.