Editing Kotahi data supply (section)

===JSON data===
The <code>customfielddatajson</code> field contains the contents of any activity. Obviously this varies between activities, and over time (if activities are modified). We will likely need some kind of mapping document to keep track of field changes and/or multiple fields which we need to perform analysis/calculations on.<ref>For example, financial summaries or client/aiga goal plans which span different services.</ref>

A fairly nice way to unnest JSON for specific tasks can be done via:

<syntaxhighlight lang="sql" line>
select distinct
a.clientid,
j."RequestDate",
j."RequestProduct1",
j."RequestAmountTotal"

from kotahi.activities a,
	jsonb_to_record(customfielddatajson) 
		as j(
			"RequestDate" date,
			"RequestProduct1" text,
			"RequestAmountTotal" float
			)

where activitytypeid  = 27 --Whanau ora request submission
‎</syntaxhighlight>