Forum Discussion

datamonitrix's avatar
datamonitrix
Regular Visitor
4 years ago

Embedded Timezone issue

I have 4 embedded dashboards in a @Blazor app, the app is hosted in Azure and the Dashboards are in PowerBI I have an A1 embedded service and we are paying almost 1000€ a month. Our @blazor App is a multi-tenant App so different customers of ours have access via Login to their private data, the dashboards are loading with JS filters with no issue. however, our customers are spread all over the world. our App is an IoT Water monitoring system and all water sensors are set to report in UTC, but we need to display the data in the customer's local time. Not an issue when there is a single last report date (I have a DAX function to handle that), the issue is when I need to add a date series to a line chart with hundreds of readings, there is no way to convert this to local time using DAX and there is no way to apply any locale or timezone logic since the powerBI service is in the cloud and our app renders the page also in the cloud the local is set by the rendering server and not by the client's browser. 
Any idea?  

Need Help

5 Replies

  • lbendlin's avatar
    lbendlin
    Super User
    4 years ago

    " the locale is set by the rendering server and not by the client's browser. "

     

    Not according to the doumentation.  The client's browser settings override the Powr BI service settings. Supposedly.

    • datamonitrix's avatar
      datamonitrix
      Regular Visitor
      4 years ago

      Thanks Ibendlin,

      I think that is not what happens when embedded. my supposition is that when it is embedded the embedding is being pre-rendered in the server, the iFarme is loaded in the server and getting locales set at this time and forwarded to the client. I am not being able to have the client's locale work with nothing I have done.


      • Anonymous's avatar
        Anonymous
        Not applicable
        4 years ago

        HI datamonitrix,

        For the language and report UI parts, they should be recognized and rendered by client user locale settings.

        Notice, these analysis steps do not include timezone transform, power bi service will clean up the timezone to convert these DateTime values to UTC format. 

        If you want to keep DateTime values with locale, I'd like to suggest you create a calculated column in your table to manually calculate fixed DateTime values based on specific date timezone offset. (power bi service convert to UTC steps will be balanced by these offsets)

        Regards,

        Xiaoxin Sheng