Just switched from sdfcli 2019.1 to 2020.2 and it ...
# sdf
c
Just switched from sdfcli 2019.1 to 2020.2 and it looks like importobjects no longer supports a "LIKE" query? I used to be able to "importobjects -scriptid custbody_foo" and import all the custom body fields that start with custbody_foo. It looks like this was taken away in 2020.2. Why?
It also appears we can longer import multiple, specific scriptids in the same call? OK: "importobjects -type ALL -scriptid custbody_foo_field1" NOT OK: "importobjects -type ALL -scriptid custbody_foo_field1 custbody_foo_field2" returns "An unexpected error has occurred".
a
Can you try importobjects -type ALL -scriptid "custbody_foo_field1 custbody_foo_field2"
If possible, please provide screenshots, Nothing was changed in the logic as far as i know. If there are multiple objects which
contains
the string passed as
scriptid
, it should download all.
Are you importing objects in a suiteapp or ACP?
c
Example 1 shows the result of the "contains" scenario. Result is "No objects were imported." Example 2 shows it working with 1 fully named scriptid specified. Example 3 shows it working with 2 fully named scriptids specified. My issue with this scenario is, apparently, related to running this from a Powershell script. I haven't been able to determine why I can run the same command in VS Code Powershell terminal (as the example shows), but doesn't work in my PS script. Still digging into that one. I wouldn't need this if I could use "contains", however.
a
Can you try 1 more thing? provide the script id like this:
scriptid customlist_gvcpa_
If this doesn't work then i will check, because there were some bugs filed for this case, Some users requested that they only want the objects to be imported which are defined in scriptid and not like all objects with matching scriptids. i will check if that was implemented.
c
customlist_gvcpa_ did not work either. Same result: "No objects were imported."