Skip to main content
ashwini.nemade
ashwini.nemade
April 8, 2024
Question

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

  • April 8, 2024
  • 25 replies
  • 0 views

Hi Appian folks,

I am getting this error on Export SQL to Excel smart service - "The following error was raised by the Export SQL to Excel function:  Name is insufficiently unique".

I have configured "Document_name_to_create" on this node by appending now() after the document name i.e. "Document Name " & now().

I understand that this error comes up when document name is not unique, although I have appended now() in the end, the error doesn't seem to resolve. How do I fix this issue?

25 replies

mikes0011
mikes0011
Brainy
April 8, 2024
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.

ashwini.nemade
ashwini.nemadeAuthor
April 8, 2024

[mention:b45a4f6a20b14a008e4e0ec732a8bf98:e9ed411860ed4f2ba0265705b8793d05]  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.

mikes0011
mikes0011
Brainy
April 8, 2024

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")

harshk1671
harshk1671
April 8, 2024

Hi Ashwini,

Can you check again if all the columns of your SQL and Excel headers are unique? Also, if you are using cell_keys, check that as well.

    ashwini.nemade
    ashwini.nemadeAuthor
    April 10, 2024

    Found the root cause here. The document name in a constant that was fetched by Copy Document Service node and the one fetched in Edit Document Properties node in case the document already exists - the document name is the same in both cases. That is why this error comes up on Export SQL to Excel node.

    So this was the data issue.

      N
      nirupamaanuragt
      January 20, 2026

      Hi [mention:f65cde4616a6499db4a4b665152ed6bf:e9ed411860ed4f2ba0265705b8793d05] 

      As I am also facing the same issue, just trying to understand if the resolution is applicable in my case too. The node property is same as is attached by you in this thread. But I am not using the edit document node.

      Apologies, I am new to Appian so trying to understand if I am missing something.

      mikes0011
      mikes0011
      Brainy
      January 20, 2026

      First can you confirm what actual error message you're getting for the pictured failed node?

      Terms & ConditionsAccessibility statement