Daxko limit field is being saved in a different field as it's just a string instead of an entity-reference. The app logic (shockingly) took care of everything once the category id was passed in, so yay!
To test:
configure Daxko Activity Finder settings at /admin/config/services/daxko2
set AF to use the Daxko backend at /admin/openy/settings/activity-finder
add/edit an AF4 block, add a category or more (by id)
save and test, only the listed categories should be available in the activity step
only the selected categories should be available in the filters and results.
Resolves https://openy.atlassian.net/browse/MAINTAIN-191
Daxko limit field is being saved in a different field as it's just a string instead of an entity-reference. The app logic (shockingly) took care of everything once the category id was passed in, so yay!
To test: