You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: