search

doug-m / CollectorAuroraTesting

Manage testing feedback for Collector holistic testing.
0 stars 7 forks source link

Map does not allow view or interaction with related records #228

Open jaraine opened 4 years ago

jaraine commented 4 years ago

Issue

Some of our maps will not allow us to view related data (other maps seem to work fine).

Expected Behavior

Should be able to click on a navigation line or species list transect, then view, edit or add mrelated data to the common species table and survey status table.

Map and Credentials

Steps to Reproduce

Open map on device and click on species list transect or navigation line and see if you have option to add, edit or view related data

Device Information

Kevin-GIS commented 4 years ago

@jaraine I was able to reproduce this issue using Android but not iOS.

In the following screenshots, the layer LP_Species is related to a table called Priority1SpeciesList. It's displayed on iOS and not Android:

iOS
Android

One strange thing I noticed when reviewing the JSON for the LP_Species layer, is that in the relationships section, the name of the related table is blank and is just an empty string where normally it should display what table it's related to:

Empty related table name

The related table Priority1SpeciesList is in the hosted FS though:

Hosted FS layers

This issue also happens to the SpeciesListTransects layer in that map as well. No related tables are accessible.

I am not sure how this data got into this state where the related table name in the JSON is blank, as I cannot reproduce it with my own data when editing the JSON.

I am not sure at this point whether this is the issue or not, but do you know how this might have happened to this data?

Thank you -Kevin

Kevin-GIS commented 4 years ago

Logged Apps-Android 1756

jaraine commented 4 years ago

Hi Kevin

Thank you for looking into this more, and I apologize for the delay in getting back to you, but things have been super hectic this week. So, I looked at the project last night, and when I look at in Classic for iOS, everything seems to be related as it should be, so I am not sure what could possibly be going on with the blank name in the JSON for the related table. My only explanation is that this is a feature layer that we have been using for quite some time, I think we first hosted it mid July of 2017, and in the process of getting things ironed out, we had to download it and serve it again a few times. The other outside possibility is that at the time, the only way we could change domains was to edit the JSON code, so I suppose it is possible that someone could have deleted the related table name, but it seems unlikely, and I am not sure why the relationships still seem to work in Classic.

One other note, for the last month or so, this hosted feature layer has been particularly problematic in terms of syncing. We get sync errors(replica errors) everytime we try to sync the data. The data does sync, but it does not show that it is syncing correctly on the device and we end up having to delete it and reload the map. We have been talking about standing down data collection and rebuilding this hosted feature layer, do you have any thoughts on if you think that might be a good idea, and if so, the easiest way to do that to ensure we don't have any data loss? I feel like the last time I tried that(a long time ago), I ended up with issues of GlobalIDs not working well, and having to assign new GlobalIDs and recreating the GUID for related data.

Thanks again for your help.

Jonathan

On Tue, Aug 13, 2019 at 12:42 PM Kevin Burke notifications@github.com wrote:

@jaraine https://github.com/jaraine I was able to reproduce this issue using Android but not iOS.

In the following screenshots, the layer LP_Species is related to a table called Priority1SpeciesList. It's displayed on iOS and not Android: iOS https://user-images.githubusercontent.com/24723464/62982166-3883da80-bde0-11e9-8c19-8fd667f255d4.jpg Android https://user-images.githubusercontent.com/24723464/62982179-45083300-bde0-11e9-806f-5e6476369432.png

One strange thing I noticed when reviewing the JSON for the LP_Species layer, is that in the relationships section, the name of the related table is blank and is just an empty string where normally it should display what table it's related to: Empty related table name https://user-images.githubusercontent.com/24723464/62982191-4fc2c800-bde0-11e9-9339-f40f712ee403.PNG

The related table Priority1SpeciesList is in the hosted FS though: Hosted FS layers https://user-images.githubusercontent.com/24723464/62982395-d5467800-bde0-11e9-8fca-a6c990e4eb5b.PNG

This issue also happens to the SpeciesListTransects layer in that map as well. No related tables are accessible.

I am not sure how this data got into this state where the related table name in the JSON is blank, as I cannot reproduce it with my own data when editing the JSON.

I am not sure at this point whether this is the issue or not, but do you know how this might have happened to this data?

Thank you -Kevin

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/doug-m/CollectorAuroraTesting/issues/228?email_source=notifications&email_token=AM3BWJXDWX62RNPEBDZX6R3QEM2GJA5CNFSM4IKD7BYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4HGEZY#issuecomment-521036391, or mute the thread https://github.com/notifications/unsubscribe-auth/AM3BWJTO3JIRM2RSQJZDUI3QEM2GJANCNFSM4IKD7BYA .

Kevin-GIS commented 4 years ago

Thank you for the feedback @jaraine, and for the explanation regarding the history of this data. I logged an internal issue to look deeper into the related table issue.

With regards to the follow-up issues with sync, are you using the map above that is reference in this issue? If so, are you currently able to download this data in Collector? When I tested this same map that was logged in https://github.com/doug-m/CollectorAuroraTesting/issues/223, I couldn't take it offline due to that issue (I explained the underlying issue in a comment in that issue).

If you can still reproduce the sync issues, can you please log another issue for that?

Thank you -Kevin

jaraine commented 4 years ago

Sorry I wasn’t more specific, I can take it offline with Classic Collector.

On Thu, Aug 15, 2019 at 2:27 PM Kevin Burke notifications@github.com wrote:

Thank you for the feedback @jaraine https://github.com/jaraine, and for the explanation regarding the history of this data. I logged an internal issue to look deeper into the related table issue.

With regards to the follow-up issues with sync, are you using the map above that is reference in this issue? If so, are you currently able to download this data in Collector? When I tested this same map that was logged in #223 https://github.com/doug-m/CollectorAuroraTesting/issues/223, I couldn't take it offline due to that issue (I explained the underlying issue in a comment in that issue).

If you can still reproduce the sync issues, can you please log another issue for that?

Thank you -Kevin

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/doug-m/CollectorAuroraTesting/issues/228?email_source=notifications&email_token=AM3BWJUKDUIG23F2Z7ORCJDQEXX6BA5CNFSM4IKD7BYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4NK5FQ#issuecomment-521842326, or mute the thread https://github.com/notifications/unsubscribe-auth/AM3BWJXO4KPYFKB5ALPSHEDQEXX6BANCNFSM4IKD7BYA .

colinlawr commented 4 years ago

@jaraine This should be fixed in the next beta update. We hope to have one by the end of the month.