The following error was raised by the Export SQL to Excel function: Name is insufficiently unique

Ashwini N said:

Name is insufficiently unique

I've only ever seen this complaint when deploying from one environment to another.  Can you clarify where and how exactly you're seeing this?  Could you include a screenshot?

Document name uniqueness (even in the same folder) is not required in Appian, and even though Export SQL to Excel is a plug-in, I wouldn't have expected it to (artifically) care about document name uniqueness either.

Mike Schmitt  So the scenario is - 

I am getting excel template from constant, editing the properties like Name (because there is a condition involved - if the document exists, get the doc_name or give it a new name) and then exporting the SQL in that template. 

Now, the SQL is prepared, document is fetched but when the process goes to Export SQL to Excel node, it fails due to specified error.

fyi, "now()" when cast to text, returns some characters that are not valid in file names (including at least 2 forward-slashes and a colon).

You should instead generate a filename-safe string and append that.  I'm not sure this is the root of your current issue, but I'd try it first anyway since you'll ultimately need to fix it anyway.

text(now(), "yyyy-mm-dd HH.mm.ss")

fyi, "now()" when cast to text, returns some characters that are not valid in file names (including at least 2 forward-slashes and a colon).

You should instead generate a filename-safe string and append that.  I'm not sure this is the root of your current issue, but I'd try it first anyway since you'll ultimately need to fix it anyway.

text(now(), "yyyy-mm-dd HH.mm.ss")

I tried it. Didn't work. Got same error - Name is insufficiently unique.

Hi Ashwini N just wanted know are you using that latest version of the plugin, Could update it to latest version and check?

The version is 3.1. There is no update available for this plugin though.

Why don't you generate a random value instead of generating the name of the document with now()?

may i know what is the warning showing on the version of your plugin?

  I tried doing that with tointeger(rand()*100000000). Didn't work. Got same error.

Abhishek Karumuru  It says that the plugin is not listed on AppMarket so Appian recommends to remove it from the environment. But this plugin, especially Export SQL to Excel smart service is used in 12 process models, with same design and all of them works fine without any errors, except this one.

Try with this for generating the value and test again please.

a!localVariables(
local!data: split(tostring(rand()), "."),
tointeger(local!data[2])
)

 Tried this logic too. Saved it in process variable and appended it in "Document_name_to_create" attribute as "Doc name " & pv!docName.

Didn't work. Same error.

Honstely by now I think we've ruled out the filename itself being the cause of this error.

Any chance you could try out the equivalent smart service either from the main Excel Tools plug-in, or from the newer stand-alone "SQL to Excel" plug-in (assuming this isn't the one you're already using), and see if the same issue happens?