Thank you for your reply. No problem Enjoy your break!
I will also post some information in this thread for easy tracking.
Thanks and cheers,
Vinia
Thank you for your reply. No problem Enjoy your break!
I will also post some information in this thread for easy tracking.
Thanks and cheers,
Vinia
Hi Hélène,
Thank you for your response. Sharing with you some more info and screenshots.
First, here's the connector from GDS:
And here are some info about my case.. I have a form with a number of child tables. But for the purpose of illustrating my issue, I will use only 3 tables from my form. My form has 3 levels => (1) Structures, (2) Households, (3) Members
In the image above, you will see that i made separate connections and did not use the Blend Data option. I will explain why later.
My parent table, Submissions, contain information about the structures. And to each structure, one or more households may be related or associated. And to each household, one or more members may be related. The household is a repeat under the structure (Submissions) and the member table is repeat under household. When I connect to the the Submissions table, here's what I get:
No problem. Correct number or count of rows/submissions or structures. But when I view the fields, here's what I get:
677 is actually the number of fields in the entire form, including the child tables. Btw, my form has about 30 child tables. And I have no problem processing and visualizing them in Qlik Sense. Going back, it seems that the parent table or data source is referencing a flat table. But it doesn't include the data. All fields of the form but data from the Submissions/parent table only. And when I create a report based on that first table, with Count and Count Distinct, here's what I get. The second column is actually a field in the Members table. I just tried to check if the table will return some values. But it did not. So maybe the table did not import the data from the child tables, only the fields. I made the wrong assumption in my first post. I thought the connection to the Submissions table also included the data from the child tables.
The first column is a field/dimension in the Submissions table and the second column is a field in the members child table. I am not sure what is being calculated in the last column when I tried to use the Count Distinct aggregation.
Moving on to the second table, the household table:
Again, the count of rows seem correct. And again, this is a repeat under Submissions.
However, it only returns one field which is the Submissions ID for the repeat. It doesn't have the PARENT_KEY that can be used to link it to the parent table. Just this single field. While all the other fields are in the first data source.
And when I try to create a report based on this table, this is what I get:
The same goes with my Members table. The data source gives the correct count during configuration. But when I create a report, it returns 0. Also with only one dimension. Only the Submission ID field in the Members child table.
I hope I was able to explain the issue clearly. If you need more information, kindly let me know.
Thanks and cheers,
Vinia
Thanks so much for that detailed writeup, @Vinia_Marciano.
This really makes it sound like there's something about your schema that the connector is unable to process correctly. We've done some amount of verification with a single repeat but none with nested or multiple repeats. Would it be possible for you to share your form definition for troubleshooting?
Yes. but can I share it privately?
Thank you.
Yes, you can send it to me and @hugh_sun in a private message. I can’t make any promise on timeline but we will try to look into it.
Hi, @hugh_sun I hope you received the form definition I sent in August. Still not able to correctly output data using the ODK connector. The Submissions table returns all the fields in the entire form and all the child tables just return one field, the id field.
If i am not doing it right, I hope you could point me to the right direction. Thanks so much in advance.
Cheers,
Vinia
Hello Vinia, unfortunately I am no longer the manager for our team this year. A new manager will take my place and his name is Sam Levy. He will introduce himself here when he has the chance and will be your correspondent from now on. Thanks so much!
Hi, @Vinia_Marciano My name is Sam and I am taking over as project manager for our team! We had a high turnover so most of our developers are new to ODK and we just started the process of onboarding. This is at the top of our priority list though! I will get back to you by the end of the week at the latest with an estimate of how long this will take us to address! Thank you so much for being so patient with us and we are looking forward to working with you more
Thank you for your response, Hugh! Hope to still see you around. Take care!
Cheers,
Vinia
Hi, Sam! Warm welcome to you. Thank you for your update and for giving this a priority. Very much appreciated
Good luck and hope to hear from you soon. The connector is really a great project (and ODK of course ) and thanks so much to all of you for working on it.
All the best,
Vinia
Hi! Wanted to check in on the expected timeline. It's a little bit of a hectic time as we are starting school and onboarding onto the project haha. I am estimating that it takes us about 3 weeks to finish a condensed onboarding and fully investigate this issue and add changes! If there are any time constraints you are under please let me know!
Hi @samlevy Sam!
I hope you're doing well. Would just like to ask if you removed the ODK connector from the GDS platform? Is it just for the time being? (I hope! )
Hope to hear from you soon!
Cheers and take care
Vinia
@Vinia_Marciano Hi Vinia!
It is just for the time being! I made a mistake deploying a new version of the connector rather than updating the current one and we have to go through the process of resubmitting it to google
This is the issue on out GitHub which has updates on the issue: https://github.com/UDub-Impact/OData-Connector/issues/27
And this is a temporary link to access the connector: https://datastudio.google.com/u/0/datasources/create?connectorId=AKfycbxMsmDvxShWuf1jctvN8B_4BKzrTXCkx1sAj2cplioeOpWgD7inx0jsnAEflDJSYuckTA
So so sorry for the confusion! We have also finished onboarding and are working on your issue! I will add more updates here as I get them!
Hi @samlevy Sam! Glad to hear that! I hope everybody's settled and well. Thank you for the updates and for the link.
Good luck and cheers,
Vinia
Hi @Vinia_Marciano Vinia!
Wanted to follow up again. We are still waiting for Google to republish the connector but we fixed the issue with the repeat tables along with some smaller bugs we discovered along the way. I am attaching a link to a temporary connector: https://datastudio.google.com/u/0/datasources/create?connectorId=AKfycbwvx0abeqBvCjqk_bhik1trRQ0--X_r58E2C6ncApjVLdU09bA3mTi26MixsFZXUwU with those changes (note that it will not be the one published).
I ran it using a submission I created using your form definition and it appeared to work for me but I wanted to give it to you so you could try it as well! Let me know if you run into any problems! Apologies it took longer than I anticipated!
Hi @samlevy Sam! This is great news! Thank you so much for the update and for working on this. Really excited to test this again. Sorry wasn't able to reply sooner. Came down with the virus, still trying to fully recover.
Will send you updates.
Thanks and cheers,
Vinia
@Vinia_Marciano Oh no I am sorry to hear that! I hope you feel better soon! We are still working on an issue with types that occurs after editing an existing connection but we're looking forward to any feedback you have on the changes we've made so far!