I have more of a workflow issue

I've been using a mix of import recipes from here as well as ones that I have written. I'm coming from the Munki world where there is a common name key that tells Munki what is going on. With the FW imports, I'm getting filesets that are numbered based on each version, as well as new fileset IDs.

Since they are new filesets, I lose my associations and the clients don't get the update.

How do you work with this since I assume that you all use the recipes that you post here?

I know that I can import them to a group, and associate the fileset group to my clients but if I go that route, I lose the kiosk functionality or I will conversely need to manually update the kiosk.

Any feedback would be appreciated.

No files, tests, or entry points are identified. The FileWave import workflow and fileset-association behavior need clarification first; done would be an agreed, documented way to preserve associations and kiosk updates.

Written by the indexing model from the issue text.