Hi GD team, using FlexConnect as a data source, we’ve noticed that setting a default value for a filter on the dashboard does not persist after a page refresh. Instead, it defaults to what appears to be the first value in the list, which in this case is an empty value. Since we’re embedding the dashboard and passing values from our side, we’re wondering if there is something we need to adjust in our embedding setup or something GD could help assist with to ensure the default values persist? Thank you! cc @Alson Yap

Hello Jennifer, Thank you for reaching out to us. Could you please provide a link to the dashboard in GoodData? Thank you.

Hi @Ismail Karafakioglu, here's the link to a test dashboard. I've set the default value to be

Scope 1

but when i refresh, the value does not stick and goes to

empty value

.

Hi Jennifer, Thank you for the link. I was able to reproduce the issue on the test dashboard and for the moment, it is not behaving as expected. I tested in my own environment and filter remains as the selected value and does not revert back to "empty value". One idea is that it might be connected to FlexConnect. Could you please try to create the same scenario but using a different datasource so we can see if it is connected to FlexConnect? Thank you for your cooperation.

Hi @Ismail Karafakioglu, I'm sorry I'm not sure what are you referring to. The test dashboard that I've created is connected to our

FlexConnect

. Screenshots below in edit mode and after refreshing, with the issue of the default value not persisting. Could you share what your results are?

Hello Jennifer, I am sorry for the confusion. I tested it on my environment and can confirm that what you see is not expected behaviour from what I have gathered so far. Thus, I am passing this ticket to my colleagues in L2. One will be here once they are available. Thank you for cooperation.

Hello @Jennifer Chue, This is Daniela with L2. 1 -May I know if the datasource is working in another workspace? 2 - Is this a new datasource? was it working before?

Hi @Daniela Salmeron, apologies the server was in development mode, have switched it to prod, it should be working now

No worries! Glad to hear that is working

@Daniela Salmeron Would you be able to assist with the above issue?

My apologies, my understanding from your last comment was that it was fixed by switching the sever to prod mode. Is this not the case?

We are still experiencing the above issue, my apologies I assumed that your questions were asked bcos the test dashboard was not working on your end due to it being in the dev mode. Would appreciate your assistance!

oh, sorry! I am able to reproduce it 🙂 Yes, my question is about ts-tmpdev-flexconnet-ds itself, as the workspace provided is using this one.

1. May I know if the datasource is working in another workspace? • Yes, the datasource is working in another workspace. This issue is consistent across different workspaces. 2. Is this a new datasource? was it working before? • No, this is not a new datasource. If you're referring to whether the default value persist previously after refreshing then no, it hasn't worked before.

May I have the workspace on which this same datasource (has the dropdown values) working? I would like to compare them

Hi @Daniela Salmeron, apologies if I misunderstood the meaning of "`working`", The datasource itself is working fine but the default values do not persist. It doesn't matter what workspace, the issue is still prevalent. I've included another test dashboard using the same datasource in a different workspace here for your reference regardless.

Thanks Jennifer! Would be possible to change the Cache Preference of the datasource? From

Optimize for real time data

to

Optimize for speed and savings

?

The cache preference has been configured this way as our use case relies more on real-time data. However, I tried changing the cache setting for the data source, and unfortunately the issue still persists.

Thanks for testing! After some testing and checking your workspace, I can see that is not related to dashboard nor workspace/user filters. Also, doesn’t look related to FlexConnect. However, I’m still unable to reproduce the issue. Therefore, I have escalated this with our engineers and we will look into it. I’ll let you know once I have more news.

Hi @Daniela Salmeron, are you able to access it now?

Yes! Thank you so much! I’ll let you know our findings

Hi @Daniela Salmeron, could I check if there has been any progress with this?

Hello! My apologies Jennifer, but our engineers are still checking on the issue. Sorry that is taking longer than expected.

@Daniela Salmeron Is there perhaps an estimate of when we can hear back regarding this issue?

Hello Jennifer, My apologies that this is taking so long. Our investigation so far shows that the issue is with the persistence of the metadata during the refresh. The metadata is there, but for some reason when refreshing the page, it goes back to the empty value. We are a bit puzzled and still trying to reproduce this issue on our end, but it is taking longer than expected. Therefore, I don’t have an ETA yet. However, I will however ping you once I have more details. I’m very sorry for all the time that is been taking.

Hi @Daniela Salmeron, thank you for the updates thus far. Wanted to raise up that this seems to be an issue across the various filter features on GD using FlexConnect currently, namely: 1. Filters showing up as None instead of actual filtered values in exports of the visualisation (End users not able to confirm actual filter values used) 2. Filters showing up as None instead of actual filtered values within visualisations, both at the left side and headers 3. Filter defaults not showing up in dashboard filters when refreshed Would we be able to escalate this issue further with number 1 being the most pressing issue? Any timelines would be greatly appreciated as well

Hello @Jennifer Chue sorry for the radio silence here! We are currently testing the fix in our testing environment and we are targeting the release to production tomorrow. I’ll let you know once is ready in Production

thanks for your reply @Daniela Salmeron, can I know if this is a fix on GD Cloud and/or GD SDK (that's being used for FlexConnect, which means we have to upgrade our library/package)?

GD SDK, but no upgrades or changes would need to be made on your end

okay good to know, thanks!

Hello! We just release the fix into Production. Can you double check on your end? Thanks!

Hi @Daniela Salmeron, thanks for the update. It seems like the original issue where the filter defaults not showing up in dashboard filters when refreshed have been resolved as it now remains when I refresh the page. Thank you very much for this. However, the other issues below that I mentioned thereafter are still happening. Are these issues being resolved as well in the fix? If they aren't, would greatly appreciate your help to look into them as well 🙏 Have set up the test dashboard for both issues here 1. Filters showing up as None instead of actual filtered values in exports of the visualisation (End users not able to confirm actual filter values used): In the test dashboard, the Scope filter shows up as None (value should be 2) when the

Test export

visualisation is being exported. 2. Filters showing up as None instead of actual filtered values within visualisations, both at the left side and headers: In the test dashboard, the Status filter shows up as None (value should be approved) when editing the

Test header filter

visualisation. Right now #1 is more of a priority issue that we hope can be resolved asap. 🙇🏻‍♀️

Hello Jennifer, Yes, I can see the 2 issues you are mentioning 😞 Let me just clarify a few things on what was done: This is what it was fixed: 1 - When selecting a default value for a dropdown in a Dashboard, the value was not being preserved. 2- If a value is chosen in the dropdown and then the page is refreshed, it goes back to “None” or to the first value in the dropdown. The issue we were having: The problem is race condition that manifested because of slow response, probably as a result of using flexconnect. This other 2 issues ( exports and when going to ‘Explore form here’) were not part of the fix on Friday. We are gonna apply the same fix. I’ll know the ETA between today and tomorrow.

Understood, thank you very much @Daniela Salmeron! Appreciate the ETA as well, pls keep us updated 🙏

Hello! We are sill checking if the same fix can be applied for both situations. I hope to have more news today at end of the day.

Got it, please keep us updated 🙇🏻‍♀️

Hello! I’m happy to let you know that the fix is in Production. Both issues are fixed, the filters work as intended. Please double check on your end and let me know how it looks. Thanks!

Hi @Daniela Salmeron, thank you very much! I can see on my end that both issues have been fixed and the filters are showing as expected now

Awesome! Thanks so much for your confirmation!

Hi @Daniela Salmeron, thank you for your help on the above issues thus far. However, it seems like the issue of an exported visualisation having "None" filters is still happening for the

Excel

format even though it has been fixed for other formats like pptx. Could you pls help to look into this?

Hello! I’m sorry to hear that! We fixed it previously for all exports. May I know when you started seeing the issue again? 😞 I’ll check what happened.

It was found this morning at about 11am/12pm SGT

Hello! Thanks for the information. I discussed this with our engineering and so far we haven’t seen any other changes made that would have affected the export for just .xls, we are currently checking further. However, I would like to share with you, that most probably the fix + testing will happen next week. My apologies about it.

Noted on this, pls keep us updated and thank you for your help!

Hello! We are estimating that the fix will be ready on Friday, I’ll let you know once in Production. If anything changes, I’ll let you know. Sorry for the delays.

Noted thanks!

Hello! I’m sorry to let you know that the fix its a bit more complex than expected and we still need a bit more of time. On Monday we are going to discuss this internally and I’ll let you know the new ETA.

Hi @Daniela Salmeron, I see noted, thank you

Hello @Jennifer Chue, We will need your help with some FlexConnect information. Can I DM you?

Hi @Daniela Salmeron, yes sure