[BUG]: REST Endpoint Datasource calls sometimes do not get the dateFilterFrom and dateFilterTo populated

[rivadblins]

SDK Version

1.7

Client Framework

Other

Server Platform

ASP.NET

Operating System

Windows

Description

When making calls to a REST Endpoint with date filter parameters, the date filter parameters are sometimes not populated.

We observed an unpredictable behaviour where sometimes the dateFilterFrom and dateFilterTo parameters were not being populated, but this was not consistent. Sometimes it was the from, sometimes it was the to. Sometimes it was neither for the same selected value.

I was not able to replicate this reliable, but did notice it happened more frequently when choosing values such as "Last 30 days" or "Previous Quarter". We had to add special parsing and handling to deal with this scenario.

Ideally, regardless of what value is selected in the date filter both the from and to should be populated, or at the very least the from should always be populated.

[MLopezIG]

We cannot reproduce this. Can you provide a sample to reproduce this problem, even if it doesn't do it 100% of the times? I can say that having reveal replace the 'from', but not the 'to', or vice versa, is something that I can't see our code allowing, unless you have a badly formed dashboard, or maybe doing something weird in your IRVDataSourceProvider implementation.

Just in case, take a look at the comment made to issue #294, it might be related and might help with this one too.

[rivadblins]

I'm not sure how I could create a sample that could replicate it without that sample going to our endpoint, is there anything else that I might be able to capture or do to provide additional information? As far as I am aware we are not doing anything out of the normal for an ASP.NET backend. Could it be related to our Vue frontend? I know Vue isn't directly supported but I'm not sure how it could cause this issue.

[MLopezIG]

We can stub the endpoint if necessary, with your help. So that's still an option to move forward IMO.

In the meantime, if you can share the dashboard, and your extension point implementations (in particular the datasource/usercontext providers) that might help too.

And if you're able to reproduce, and can capture the request/response (e.g. from the 'Network' tab in Chrome's Dev tools), as well as what you see in your endpoint, it can complement the other information here.

We don't think using Vue is related.