Problems Attaching Data File to Data Source Record from within custom Flow

[cj9r]

I am using a custom Flow with IntegrationHub to create an integration with Bit Discovery via their REST API.  I have successfully created a new action with a REST step to connect to Bit Discovery and have successfully run my flow to create an attachment on an arbitrary record I created for testing purposes.

My plan, however, for processing this attachment was to attach it to a Data Source record that I had configured with the following specs:

Type: File

File retrieval method: Attachment

Format: JSON

Path for each row: /assets/assets

When I attempt to go into the Flow Designer, however, and configure an input of type "Reference" to point to this Data Source record, the table selector will not show me the Data Source table as an option.  Additionally, I also attempted to use the "Look Up Records" step to select this record and again, the Table selector does not display the "Data Source" table as an option.

In troubleshooting this I have:

1. Looked into cross-application scope permissions and general ACL issues

For both the Data Source table (sys_data_source) and for the Attachments table (sys_attachment), I went in to Configure Table -> Application Access and enabled all CRUD permissions (they were both already set to being Accessible from All Application Scopes) in case it was a cross-application scoping issue, but those changes had no effect.  I also attempted to mirror the ACLs to be the same as my test table (which does work and is in the application I created for this integration). I am logged in currently with an account that has full Admin rights on our Dev instances, fyi. 

2. Played with the scope of the Data Source record

I created both a new Data Source record that was in the Global scope and a second one that was in my new custom application scope.  Then I tested whether I could select either of these in Flow Designer, but I still cannot select the table to even get to row selection.

3. Tested directly by manually attempting to attach a file to the Data Source records in question.

After setting my own account application scope to my new application, I can attach a file no problem to the Data Source record which is in my new custom application scope. 

If I attempt to attach a file to the Data Source record created in the Global scope, however, I get the message, "This record is in the Global application, but Bit Discovery Integration Spoke is the current application.  To edit this record click <here>".  If I click the link to edit the record, it allows me to click the paperclip and choose a file, but when I choose the file and click "Open", the green "processing" bar appears, then disappears, and no file is added to list (e.g. it silently fails).

Does anyone know why I cannot select a Data Source record from within my custom Flow as the storage location for my attachment?

Thanks!

[kemmy1]

Same problem with Orlando.  I have not received an answer yet on this.  This is very frustrating.  I was hoping to create a record on Data Source table.  I see no reason why I can't do this with Flow Designer.  😞

[Miguel Donayre]

So in order to attach an attachment to a Data Source record, you have to do the following (note- you have to have a Data Source already created)

You pull in the Lookup record action (OOTB) and set the table to the Data Source table.

set the condition to look up you predetermined Data Source record in my case the name of my Data Source was called "AWS s3 import sheet.

and it will create the data pill 

now you can reference that on the attachment action 

I am using an AWS S3 spoke and attached a record to the Data source and it works for me.

[cj9r]

Just saw your comment pop up in my email.  I actually did get this working, although I was never able to get HI to explain WHY this worked.  There is a system property (in sys_properties table):

glide.ui.permitted_tables

with a description of:

"List of system tables (beginning with "sys_", comma separated), that are reportable. By default, system tables are not reportable."

I discovered that this property identically matched the system tables that are presented for selection in Flow Designer.  I added sys_data_source to this property and was then able to select it within Flow designer.  

The only caveat I will add is that I did a lot of testing with this property and sometimes the system seemed to pick up the change in the property and sometimes it did not (I think caching was involved).  Hopefully if you try this it will smoothly and quickly pick up the change for you, but if not, you can try 1) Clearing the cache with '<Service Now URL >/cache.do' or 2) submitting a Hi ticket for them to restart the node.  

Good luck!

[kemmy1]

You should mark your own answer to this as "correct" because this is exactly what I had to do as well.  🙂