Cannot update data field in Multi Row Card without stacking up the rows. - Power BI Web App

[jack_thomas]

In Multi-Row Card, updating Value data field always stacks up the same row and then updates. Is it possible to update the changed data field in the same row so that I do not have to scroll. This case is in Power BI Web application and not in Desktop

Please find the image below.

Is it really possible to prevent repeating Tag and Message rows and update new values in the same rows so that everytime I can see only two rows.

Thanks,

jack

[v-haibl-msft]

@jack_thomas

Are you able to repro this issue in Power BI Service? What is your data source here? Do you mean that the original data was changed in the data source, but the original data was not changed in the multi-row card visual, instead, new data was added there? Is it reproducible with other visuals?

Best Regards,

Herbert

[jack_thomas]

Hi @v-haibl-msft

Thanks for reply and extra information,

In my application, I am using OPC UA Gateway to send data to IoTHub. The created StreamAnalytics job in Azure sends this data to PowerBI DataSet (Power BI as output in Stream Analytics query). I have parallely saved data from OPC UA Gateway inside Azure Blob storage. I am sharing the data format with you as a code below.

{"Data_Value_Integer":2,"Data_Value_Text":"TT101_1","Display_Name":"Tag","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:35:57","Status_Code":"Good","Variable_Description":"Unique label of the device in the plant","EventProcessedUtcTime":"2017-10-04T16:36:12.0768637Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:36:12.9700000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:36:10.3830000Z","StreamId":null}}
{"Data_Value_Integer":2,"Data_Value_Text":"MESSAGE_22","Display_Name":"Message","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:35:57","Status_Code":"Good","Variable_Description":"Field can be used in any way","EventProcessedUtcTime":"2017-10-04T16:36:12.0768637Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:36:12.9700000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:36:10.4140000Z","StreamId":null}}
{"Data_Value_Integer":2,"Data_Value_Text":"DESCRIPTIOR_12","Display_Name":"Description","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:35:57","Status_Code":"Good","Variable_Description":"Description of the device type","EventProcessedUtcTime":"2017-10-04T16:36:12.0768637Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:36:12.9700000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:36:10.4140000Z","StreamId":null}}
{"Data_Value_Integer":22,"Data_Value_Text":"DESCRIPTIOR_12","Display_Name":"Final assembly no","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:35:57","Status_Code":"Good","Variable_Description":"Field can be used in any way","EventProcessedUtcTime":"2017-10-04T16:36:12.0768637Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:36:12.9700000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:36:10.4140000Z","StreamId":null}}
{"Data_Value_Integer":23,"Data_Value_Text":"DESCRIPTIOR_12","Display_Name":"PV % range","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:35:57","Status_Code":"Good","Variable_Description":"Percent of Range- Variable that tracks the Digital Value representation with respect to the range defined by the Lower Range Value and Upper Range Value, for normal operating modes. The units of this variable are always in percent.","EventProcessedUtcTime":"2017-10-04T16:36:13.1863212Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:36:14.0480000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:36:11.2470000Z","StreamId":null}}
{"Data_Value_Integer":0,"Data_Value_Text":"DESCRIPTIOR_12","Display_Name":"Loop current","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:35:57","Status_Code":"Good","Variable_Description":"Loop Current- loop current value as perceived by the device","EventProcessedUtcTime":"2017-10-04T16:36:13.1863212Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:36:14.0480000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:36:11.2780000Z","StreamId":null}}
{"Data_Value_Integer":2,"Data_Value_Text":"DESCRIPTIOR_12","Display_Name":"HART serial no","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:35:57","Status_Code":"Good","Variable_Description":"Unique serial number related to the protocol","EventProcessedUtcTime":"2017-10-04T16:36:13.1863212Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:36:14.0480000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:36:11.8250000Z","StreamId":null}}
{"Data_Value_Integer":12,"Data_Value_Text":"DESCRIPTIOR_12","Display_Name":"Sensor 1","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:35:57","Status_Code":"Good","Variable_Description":"Sensor of channel 1","EventProcessedUtcTime":"2017-10-04T16:36:13.1863212Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:36:14.0480000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:36:11.8250000Z","StreamId":null}}
{"Data_Value_Integer":12,"Data_Value_Text":"TT101_45","Display_Name":"Tag","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:36:40","Status_Code":"Good","Variable_Description":"Unique label of the device in the plant","EventProcessedUtcTime":"2017-10-04T16:36:42.5152067Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:36:43.3360000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:36:41.2110000Z","StreamId":null}}
{"Data_Value_Integer":12,"Data_Value_Text":"MESS_123","Display_Name":"Message","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:36:55","Status_Code":"Good","Variable_Description":"Field can be used in any way","EventProcessedUtcTime":"2017-10-04T16:36:56.8275226Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:36:57.7200000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:36:55.4910000Z","StreamId":null}}
{"Data_Value_Integer":12,"Data_Value_Text":"DES_775","Display_Name":"Description","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:37:23","Status_Code":"Good","Variable_Description":"Description of the device type","EventProcessedUtcTime":"2017-10-04T16:37:24.1240591Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:37:25.0500000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:37:22.4200000Z","StreamId":null}}
{"Data_Value_Integer":25,"Data_Value_Text":"DES_775","Display_Name":"Final assembly no","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:39:03","Status_Code":"Good","Variable_Description":"Field can be used in any way","EventProcessedUtcTime":"2017-10-04T16:39:05.3783593Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:39:06.2680000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:39:03.6980000Z","StreamId":null}}
{"Data_Value_Integer":32,"Data_Value_Text":"DES_775","Display_Name":"Sensor 1","Device_Instance":"TTX300_Device_1","Server_Timestamp":"10/04/2017 18:40:37","Status_Code":"Good","Variable_Description":"Sensor of channel 1","EventProcessedUtcTime":"2017-10-04T16:40:39.4931428Z","PartitionId":0,"EventEnqueuedUtcTime":"2017-10-04T16:40:40.3120000Z","IoTHub":{"MessageId":null,"CorrelationId":null,"ConnectionDeviceId":"PublisherGateway","ConnectionDeviceGenerationId":"636409893936228674","EnqueuedTime":"2017-10-04T16:40:37.5250000Z","StreamId":null}}

In this file you can observe that when a DataValue_X (X - Text or Value) of any variable depicted by Display_Name changes, it triggers a new message to IoTHub and so to PowerBI.

Current behaviour is when it receives an update to variable the Multi-Row Card visual shows update DataValue in a new row.

My expectation is it should update DataValue in already mapped row.

I wonder if it is possible by some filter configuration?

regards,

JackDataSet

[v-haibl-msft]

@jack_thomas

How about the result if you use three separate Card visuals instead of a Multi-Row Card?

Best Regards,

Herbert

[jack_thomas]

Hi @v-haibl-msft

Thanks for reply and suggestions

Currently I am using the same solution. Using multiple Multi-Row Cards for each Variable. 

But it is not what we expected. It would be great if the variable's Data_Value updates without stacking up the rows. 

 regards,

Jack

[jack_thomas]