The data-driven content object enables you to display your data in a custom third-party visualization, within your SAS Visual Analytics report. The third-party visualization can be authored in any JavaScript charting framework, such as D3.js, Google Charts, or CanvasJS. The visualization in a data-driven content object receives its data query from SAS Visual Analytics, and so it interacts with filters, ranks, and object actions in the same way as the other objects in your report. For information about creating third-party visualizations for data-driven content, see Programming Considerations for Data-Driven Visualizations in SAS Visual Analytics: Reference.
Although is a great approach, the function converting the incoming date as a string to SAS date representation, only works when the browser is on 'en-us' locale and also does not cover all types of VA date representation.
My suggestion is to the DDC incoming data sent from VA, to provide SAS date (and/or datetime) as SAS representation (numeric) the same way it does for Time columns.
Hi @Joao-deOliveira. I agree with you that the message coming from VA could have dates represented differently - this is a nice feature request. Unfortunately this GitHub project doesn't have any control over the JSON message passed to the DDC.
rluppi
commented
3 years ago
Although is a great approach, the function converting the incoming date as a string to SAS date representation, only works when the browser is on 'en-us' locale and also does not cover all types of VA date representation.
My suggestion is to the DDC incoming data sent from VA, to provide SAS date (and/or datetime) as SAS representation (numeric) the same way it does for Time columns.