-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1 - handle ManyToMany and OneToMany fields for Trek and POI #5
Labels
Comments
Trek:Fields appearing in API to import with mapping:
Fields appearing in API to import without mapping (all values from source should be present in GAG before the aggregation, thus imported manually):
Fields not appearing in API:
Fields appearing in API but not interesting to import:
|
|
IdrissaD
added a commit
that referenced
this issue
Apr 28, 2022
IdrissaD
added a commit
that referenced
this issue
Apr 29, 2022
IdrissaD
added a commit
that referenced
this issue
Apr 29, 2022
IdrissaD
changed the title
1 - handle ManyToMany fields for Trek and POI
1 - handle ManyToMany and OneToMany fields for Trek and POI
May 2, 2022
IdrissaD
added a commit
that referenced
this issue
May 2, 2022
IdrissaD
added a commit
that referenced
this issue
May 2, 2022
IdrissaD
added a commit
that referenced
this issue
May 2, 2022
Handle ManyToMany and OneToMany fields for Trek - #5
IdrissaD
added a commit
that referenced
this issue
May 2, 2022
Handle ManyToMany and OneToMany fields for Trek - #5
POI:Fields not appearing in API:
|
|
IdrissaD
added a commit
that referenced
this issue
May 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
sources, themes, ratings, networks, etc.
The text was updated successfully, but these errors were encountered: