Executing transformation from Cognite Function

Is it a good practice to execute transformations from a Cognite Function?

Our team implemented a Cognite Function which executes transformations on tables from Cognite RAW. We chose this solution as we wanted to parametrize the SQL query of the transformation, essentially applying a different filter on raw tables every time.

Also, it would easier for the end user, e.g. a plant operator, to provide a JSON input to the function then to edit the query every time in multiple locations. E.g., if the JSON is:

{
  "plant": "Plant.1",
  "equipment": "equipment.1"
}

the user can just change the ID for the plant and equipment. Furthermore, these values can be validated by the function before making the replacements in the query and executing the updated transformations.

Let me know your thoughts!