You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add “Field Instructions” data from ContactFields endpoint and place it into the schema field called “Description”
This way people can configure fields in Wild Apricot and document their use in Wild Apricot and this will propagate to the reporting system as part of a “data dictionary”.
Beach Pass2 for example on the sandbox site has some instructions to test with.
This should be implemented generically because there are registration form fields as part of the Event Registrations endpoint that have field descriptions too.
The text was updated successfully, but these errors were encountered:
This would require a refactor, currently fields are aggregated in getData() mapped from schema field name -> api field name. This requires us instead to map in getSchema() from api field name -> schema field name. I can do it but it'll probably be at least 2 hours.
@stephenpoole let's hold off for now on this -- it's really a utility for report makers to help them identify which fields they are looking at. It's useful for custom fields on Contacts and event registration forms for custom fields which we are not yet supporting.
Add “Field Instructions” data from ContactFields endpoint and place it into the schema field called “Description”
This way people can configure fields in Wild Apricot and document their use in Wild Apricot and this will propagate to the reporting system as part of a “data dictionary”.
Beach Pass2 for example on the sandbox site has some instructions to test with.
This should be implemented generically because there are registration form fields as part of the Event Registrations endpoint that have field descriptions too.
The text was updated successfully, but these errors were encountered: