@ramrexx This did help me find the value, though a little bit funky.
I needed to have a dialog_tag_0_service_name (which would allow for Ansible Tower inventory sync to bring it over in the metadata as a tag. This worked for the Ansible piece, but the service naming (if not automatically determined) needed to come from dialog_service_name, so the service would get named based on users choice. (I just wrote a couple lines in dialog_parser to check and set values).
Been travelling last few days, so I haven't tested everything to make sure it is functioning as I intended. I'll likely go back and clean it up once I get more familiarity and/or a better way to accomplish what I'm attempting to do.
In the end, the service name will be used to generate a directory services security group. This will be created through ADEdit, add the user who requested to that security group, attach the group to the server(win or linux). Just means that all 5 servers together will have 1 access group by default to represent the owner(s).