Generating documents directly to SharePoint

[Modesto Vega]

I suspect I know the answer but don't like to make assumptions.

Is it possible to generate documents directly to a SharePoint document library?

[shimon]

Hi,
I just did. I guess that to really make it count, I would have to go into SP and fill out all the required fields and check it in.

OK. I just checked it in, and of course I cannot generate it again without checking it out first. I checked it out and was able to re-generate the document, but as I guessed would happen, this re-generation deleted the first copy and created a brand new document without leaving any trace of the first version.
I wrote to Sparx about this behavior ( this happens with any document that is linked in EA, even if it is in a note), but have not received any substantial response.
If you want to do this process as a one timer, go ahead. You must take into account that anybody that comes after you and re-generates a document with the same name will delete any versions that you wrote.

This is all under the assumption that you have delete permissions on Sharepoint.

Sincerely,
Shimon



 

[Modesto Vega]

Thanks Shimon.

We do not use check-in/out in all of our document libraries. Overwriting the document within keeping a version history is a really serious issues that Sparx Systems should address. Have you raised this as bug, happy to give it more visibility by also reporting it.

The process we currently used bypasses the version history as follows:
1) we generate a local document to OneDrive for final modifications, and
2) manually upload it to SharePoint, specifying that we want to replace the current version, with the end result of creating a new version.

This is a very manual process which could be greatly improve, hence the question.

[shimon]

Hi,
I corresponded to Sparx Support by email.

It's hard to call it a bug, as EA treats the Sharepoint as a file directory. It is Sharepoint that treats this process as a "delete and upload a new file with this name for me".
We are currently not using Sharepoint as the repository of linked files because of this issue.

Sincerely,
Shimon


 

[Modesto Vega]

At the very least, it should be treated as an enhancement to existing functionality.

[shimon]

I suspect that there are not enough Sharepoint users to make it worthwhile.

[Modesto Vega]

I suspect that there are not enough Sharepoint users to make it worthwhile.

I sincerely hope the stakeholders that make purchasing decisions where I work don’t see the above. IMHO, having an EA tool running on Windows that doesn’t integrate well with SharePoint and other products on Microsoft’s offering is not exactly a unique selling point.