Flow Designer using Record producer to populate a list collector field

[CA7]

I have attempted to use the following solution in Flow Designer to populate a List Collector field from a Record Producer with no success:

Flow Designer: For Each action with List Collector and Approval 

flow-designer-for-each-action-with-list-collector-and-approval

The Record Producer is oob and it is called 'Reclaim Asset' from the HAM installtion.

The asset variable is built off the Asset Reclamation Request [asset_reclamation_request] table with the Asset field being the list collector and a reference qualifier associated to the requested_for for table alm_asset: javascript: 'assigned_to='+current.variables.requested_for+'^sys_idNOT IN'+new AssetReclamationUtil().getAssetsToExclude(current.variables.requested_for);

This field has an onChange client script against a field 'Employee Separation'. that auto populates the alm_asset records associated to the requested for.

No matter what, I am unable to activate the Data Pill Picker for the field. I thought it might be due to an issue with my action but seriously do not think so. Also in Flow designer, I am unable to manually do the select of the assets.

My next troubleshooting approach was to take a copy of the oob reclaim asset rp and inactivate the client scripts since i am doing the work in the flow. still no luck.

When I click on the down arrow, nothing happens. It is not functioning even though I am using the oob Reclaim Asset RP or my copied version with a simple reference and no background calls to the script include utility.

Any ideas?

[Jason_DaSilva]

Any one got any further with this?  I thought that since the field requires a List(alm_asset), that creating a subflow that would output a list of sys_ids (based on assigned to and state) that I could use that data, but it too fails (List in not allowed here).
I have not gone the route of doing the look up within the Flow itself and making a glide record... will try that next.

[TomD MCC]

Looking to see if anyone has a solution for this

[Jason_DaSilva]

My manager put in a ticket on this and it seemed way back then to be a known issue.  After a few months we shifted away from this, but eventually as we clean up or Asset process, we are going to need this to work as well...

[MdZayeemB]

I believe we may be overlooking a fundamental point here. A Record Producer is a specific type of catalog item that enables end users to create task-based records, such as incidents, through the Service Catalog.

Since we are using Flow Designer, and there are out-of-the-box actions available to directly create records in the target tables, do we really need to Record Producer for this purpose? Just a thought for consideration.

Additionally, the Record Producer approach may still be relevant if there is a business requirement where the flow or action contains logic to create one or more records in other tables. In such scenarios, the Record Producer action can be configured to abort the default record insertion and instead rely on the custom logic to create the required records.