Clarity on import behaviour with asset paths vs asset urls

[richardfrankza]

Thanks for all the work on Feedme.

There seems to be different functionality whether you import from a file path versus an asset url

When the JSON has a file path, FeedMe expects there to be an Asset already created - it does a search using criteria that includes the filename, and if it doesn't find the asset, it doesn't create a new asset.

When the JSON has a URL, Feedme gives the option to create new assets etc.

I find this poorly documented and confusing in the UI. Can there be further help text that explains this difference.

And should this difference exist? I expect whether I'm pulling a file from the local file system or from a URL to get the same functionality options (e.g. replace asset if exists).

[i-just]

Hi, thanks for reaching out! This works as expected right now.

When importing to an Assets field, you need to provide the filename (not a path) of an existing asset or a URL for a remote file you’d like to upload and relate via the field: https://docs.craftcms.com/feed-me/v4/content-mapping/field-types.html#assets.

If you have a feed importing into the Asset element type, you can use the local path to import locally stored elements. The details of how to do that and what other options are available are here: https://docs.craftcms.com/feed-me/v4/guides/importing-assets.html.

I hope that clarifies things a bit!