Cannot create attachment in Non-Draft Entity.

[pallavjadav]

Hi SDM Plugin Team,

We are trying to implement a scenario where, we just need to show a object page with Attachment table but un editable basically non-draftable entity.
We are looking to store the attachment from nodejs backend and the same should appear on the attachment table.
We are aware of the createAttachment within test files of this plugin where we are creating the attachments from backend but I am unable to implement that.
Do we have any alternative apis or solutions that we can use to store the attachment to dms service and reference the same on the attachment table.

Thanks in advance.

Best Regards,
Pallav

[github-actions]

🤖 AI Summary & Recommendations

Error: Could not generate a summary and recommendations for this issue.

[dheerasameerk]

@pallavjadav Attachment can be created only in the draft mode. When you are calling the OData API to create the attachment, you need to enter the draft state first. Are you doing this step? Also once the attachment is created, you need to exit the draft state and set the state to Active.

[pallavjadav]

@dheerasameerk We are not doing any draft save, as this is object page which view only page, User can only see the attachment, which are being generated by backend and stored on DMS. Is there any possibility to show the attachment, cuz I am able to create folder, create attachment but only problem is on UI i am unable to see the link under Attachment.

[dheerasameerk]

@pallavjadav Can you please share how you created the folder and attachment from backend, specifically which API did you use and how did you validate that they are created?

[pallavjadav]

HI @dheerasameerk , I used below methods to create folder and create attachment.
----create folder ------
createFolder: async function (req, credentials, token, ID) {
// const upID = user
const { repositoryId } = REPOSITORY_ID;
const folderCreateURL = credentials.sdm.uri + "browser/" + REPOSITORY_ID + "/root";
const formData = new FormData();
formData.append("cmisaction", "createFolder");
formData.append("propertyId[0]", "cmis:name");
formData.append("propertyValue[0]", ID);
formData.append("propertyId[1]", "cmis:objectTypeId");
formData.append("propertyValue[1]", "cmis:folder");
formData.append("succinct", "true");

    let headers = formData.getHeaders();
    headers["Authorization"] = "Bearer " + token;
    const config = {
        headers: headers,
    };
    return await module.exports.updateServerRequest(folderCreateURL, formData, config);
},

----- create attachment ----

createAttachment: async function (data,credentials,token,parentId ) {

    const documentCreateURL =
        credentials.sdm.uri + "browser/" + REPOSITORY_ID + "/root";
    const formData = new FormData();
    formData.append("cmisaction", "createDocument");
    formData.append("objectId", parentId);
    formData.append("propertyId[0]", "cmis:name");
    formData.append("propertyValue[0]", data.filename);
    formData.append("propertyId[1]", "cmis:objectTypeId");
    formData.append("propertyValue[1]", "cmis:document");
    formData.append("succinct", "true");
    formData.append("filename", data.content, {
        name: "file",
        filename: data.filename,
    });

    let headers = formData.getHeaders();
    headers["Authorization"] = "Bearer " + token;
    const config = {
        headers: headers,
    };
    const response = await module.exports.updateServerRequest(
        documentCreateURL,
        formData,
        config
    );
    return response;
}

using CMIS repo explorer i can see attachments getting created in DMS.
but manually when i update the table with the url and folder object ids, i cannot see the links appearing in attachment table.

[dheerasameerk]

@pallavjadav The CAP plugin is supported only with OData APIs. What I understand is that you are calling CMIS APIs to directly create the documents and folder on SDM and then manually processing the attachments table. I not sure if this will work as this is not a use case of CAP Plugin. Can you use the CAP Plugin and the CAP OData APIs to create attachments as I suggested?

[pallavjadav]

@dheerasameerk When you say cap odata apis, do we have a list of APIs for that? where can i find it?

[dheerasameerk]

Please check this test where attachment is created using OData APIs. The test calls the OData APIs defined here.

[pallavjadav]

@dheerasameerk Yes I am aware of those apis but i am not sure how can we call the same within our service. Can you help with an example. I have tried below.. it did not work

            var doc = await zbuvcm55145dms.send({
                method: "POST",
                path: `/FIReportAttachement('<userid>')/attachments`,
                data: postData,
                headers: config.headers
            })

giving below error :

{
  code: 501,
  message: "The request has no query and cannot be served generically.",
  numericSeverity: 4,
}

[rashmiangadi11]

@pallavjadav
https://github.com/cap-js/sdm/blob/develop/test/integration/api.js#L159 Ccan you please check if this is helpful. If required you can schedule a meeting to discuss further.

[ZEN-RIVER]

@pallavjadav Any luck on this? I am trying the same thing, fetching content through external service and update it to attachments through handler,

@dheerasameerk I tried a combination of srv.create(root) → srv.create/Patch (root.attachments.drafts) → srv.PUT (attachments ) → srv. Save and many others, it just doesn't trigger the draftsavehandler for any sort of combination.

[ZEN-RIVER]

Weird way to do it, but this can be done by adding your own subaccount destination in the package, and then using it to post to own service, there could be a better way to do it.