Quantcast
Channel: SCN: Message List - SAP HANA Developer Center
Viewing all articles
Browse latest Browse all 9165

Re: Manage multi-table insert using OData Service

$
0
0

Hi Thomas,

 

Thanks for the reply.  Is this still the recommended way to create/update entities with many-to-many parent/child associations?  I am using the trial landscape (SPS 8.5?). One thing I noticed, I don't see a CSRF token in response to a GET request to my service. I am assuming this is why I am getting null for my token in getCSRF().   

 

get-resource-xsodata-req-body.png

 

get-resource-xsodata-response-hdrs.png

 

Here is my data model:

 

    Entity Resource

    {

        key ID: String(10);

        NAME: SString not null;

        DESCRIPTION: SString;

    };

 

    Entity ComplianceRequirement

    {

        key ID: String(10);

        NAME: SString not null;

        DESCRIPTION: SString;

        NOTES: String(500);

        RENEWAL_CYCLE: association to ComplianceModel.RenewalCycle;

    };

 

    Entity ResourceComplianceRequirement

    {

  key RESOURCE: association to ComplianceModel.Resource;

  key COMPLIANCE_REQUIREMENT: association to ComplianceModel.ComplianceRequirement;

    };

 

 

 

Here is my service definition:

 

service {

  "yyy.zzz.ComplianceTracker.data::ComplianceModel.Resource"

  as "Resources"

  navigates ("ToResourceComplianceRequirements" as "ResourceComplianceRequirements")

  create events(before "yyy.zzz.ComplianceTracker.services:resourceComplianceRequirements.xsjslib::createResourceBeforeExit")

  ;

 

  "yyy.zzz.ComplianceTracker.data::ComplianceModel.ComplianceRequirement" as "ComplianceRequirements";

  "yyy.zzz.ComplianceTracker.data::ComplianceModel.ResourceComplianceRequirement" as "ResourceComplianceRequirements";

 

  association "ToResourceComplianceRequirements"

  principal "Resources"("ID") multiplicity "*"

  dependent "ComplianceRequirements"("ID") multiplicity "*"

  over "yyy.zzz.ComplianceTracker.data::ComplianceModel.ResourceComplianceRequirement"

  principal ("RESOURCE.ID")

  dependent ("COMPLIANCE_REQUIREMENT.ID");

}

 

 

Here is the request payload I am envisioning for create:

 

{

  "ID": "0",

  "NAME": "TESTNAME",

  "DESCRIPTION": "TESTDESC",

  "ResourceComplianceRequirements":[

{"RESOURCE.ID": "0", "COMPLIANCE_REQUREMENT.ID": "1"},

{"RESOURCE.ID": "0", "COMPLIANCE_REQUREMENT.ID": "3"},

{"RESOURCE.ID": "0", "COMPLIANCE_REQUREMENT.ID": "5"},

{"RESOURCE.ID": "0", "COMPLIANCE_REQUREMENT.ID": "7"}

   ]

}

 

Thanks and Regards,

Neal


Viewing all articles
Browse latest Browse all 9165

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>