I tried making it a batch macro and you're right, the build complains that it can't find the function if it's not in a loaded macro file. There's no work-around for this, but I can log a feature enhancement to add an escape sequence that prompts the user for a value, similar to aliases. The first solution should still work, but your team will just have to coordinate on loading that macro file manually.