Push Targeting Dashboard UI improvements about legacy-ionic-cloud

[ericb]

Hey @sagivf 👋

Was this confusing because you collect a secondary email and store it in the custom properties, or more in the way that you had once saved an email property under custom, and then realized it was already in details?

The spinner I definitely agree with.

[sagivf]

Hi @ericb 😄
I'm actually not sure how the custom email property got there. I thought It was something you guys add. I can't find anything in my code that should be doing it, but I might have saved it there at some point.

I don't see it here either on any of the users:

Do you not see it on other users/apps?

It's worth checking, but the simplest thing would be to keep the details.xxx properties sorted to the top of the list...

[sagivf]

Thing is I've tripped over this a few times and always think there is something wrong in the system till I realise what's really wrong...

[sagivf]

Oh and I just read whats you wrote again - no, I'm not collecting a second email. not sure how this property got there 😮

[ericb]

Ah, okay. Yeah, those fields are populated by custom properties you've saved at any point for an app. So if you had a single save early on that had email in the custom properties, it would have stored that field for future lookup.

There's a number of things we may do with that system in the future, but one of the things we could do in the short term is to provide a way to delete the lookup fields (this wont remove data from users, only remove it from the lookup table so that it would not show in the dropdown list).

This way fields that may be added during development can be cleaned up when you know you're not using them anymore.

[sagivf]

Yep - that sounds good 👍 feel free to rename the issue or close it. I would however reorder or emphasis details vs custom sections - it's easy to not notice which one you are on.

[ericb]

I'll keep this open for now, since I believe both of those suggestions to be a good thing for us 👍