Closed jonsnowpt closed 12 months ago
Note Already addressed as part of issue β€ #6 . Implemented, awaiting
π deployment
.
Note Testing on
DEV
was a success, with_my_
account having the data onFirestore
andCRISP
updated correctly, as an increment was visible fromcompetitions_number: 10
to11
and so didCRISP Associated Profile
data.
Important Currently, due to the nature of the data from
competitions
using nestedJSON
data forparticipants
, all data for allcompetitions
are retrieved, analysed, and updated for each participant present in a competition. This is because it's quicker and simpler to search by simply retrieving allcompetitions
data, rather than query byJSON
as a nested format.Because of this, upon each user login, each competition participant will have their
competition_number
updated onFirestore
, but not onCRISP
. As theCRISP
is limited to the supplieduid's
. So if a user logs in, it will only update theirCRISP
Profile data.
@migbash Update on last active
Does a duplicate issue exist?
π€ Is feature request related to a problem? Please describe the problem.
No response
π Feature Request Description
Since we must contact users to welcome them to the platform and inform them about essential features, we must integrate Crisp chat to gather the most relevant user data.
DATA TO BE ADDED TO CRIP USERS:
The data is added on registration and updated in every login.
β Further context and resources (cumulative)
We need to add the number of competition participations into the Firestore user profile:
This data can be gathered from the Hasura db:
competitions/data
How to add users and integrate custom data:
https://help.crisp.chat/en/article/how-can-i-automatically-set-custom-data-1xh7pqk/
https://docs.crisp.chat/references/rest-api/v1/#add-a-people-event
[22/09/2023]
Upon testing, it was noticed that the initial data for endpoint
.../website/:website_id/people/events/:people_id
does not update the correct segment ofcustom data
as expected. Instead, the use of the.../v1/website/{website_id}/people/data/{people_id}
and/or.../v1/website/:website_id/people/data/:people_id
endpoints.