Grooper 23.00.0020 is available as of 5-15-2023! Check the  Downloads Discussion  for the release notes and to get the latest version.
Grooper 21.00.0073 is available as of 5-19-2023! Check the  Downloads Discussion  for the release notes and to get the latest version.

Mapped Export to SP or AX

jmcmanusjmcmanus Posts: 27 admin
in The Astronauts (Q&A)
Having this issue with both SP and AX.  If I export a file that has the same index values as a file that already exists, it fails.   Even though I have configured both AX and SP to allow duplicate indexes.   I can manually put a file in either with duplicate indexes.   Only time it fails is through Grooper.   Is there a setting I am missing somewhere?

Answers

  • rmccutcheonrmccutcheon Posts: 756 ✭✭✭
    For your CMIS AX connection did you set Ignor Duplicate Index to True? Ill post a screenshot let me know if that works

  • jmcmanusjmcmanus Posts: 27 admin

  • jmcmanusjmcmanus Posts: 27 admin

  • jmcmanusjmcmanus Posts: 27 admin
    error is the same for each, AppXtender Web Service Failure.  The same index has been found in an existing document. 
  • jmcmanusjmcmanus Posts: 27 admin
    Also, I don't see the same option in the SP CMIS connection, is it in a different location there, or called something else?
  • jlunsfordjlunsford Posts: 137 mod
    Can you call in to support 1-888-408-5668
  • strotellistrotelli Posts: 40 admin
    Does this AX Application use unique key on any of the fields?
  • jmcmanusjmcmanus Posts: 27 admin
    No, that was the first thing I checked.  No unique keys.   and I have the exact same problem with SP and SP 365.  my work around has been to set up a hidden field and output the GUID to that field.   

  • jmcmanusjmcmanus Posts: 27 admin
    and this isn't based off of one field.  if one field is the same it will output fine.  it is only an issue when all mapped fields are the same as a existing document in AX or SP. 
Sign In or Register to comment.