no, that's currently not supported, but its something I like to support in the future, for now what you can do to go around this is do a call to the parser from the inside of your resolver, so make the input just #{:workload/id :workflow/biz-factors}, then inside the resolver you can run: (parser env [{:workload/biz-factors [:biz-factor/id :biz-factor/name]}]) (`parser` can be extracted from the env)

note: if you are using the parallel parser, the return of parser will be a channel, you need to read from it to get the result map

but depending on how is your resolver for biz-factors, you may not need any of this, if there is only one entry for it, and you don't need something inside to be computed, you can just require the biz-factors and read from it

makes sense?