Hi Chamari,If I understand your requirements correctly, you need to create both parent and child records in a single call for an entity, correct?In that case, I believe you can utilize the nestedwithcrud functionality. You can define the structure as shown below and then pass the structure as a parameter to the action. Subsequently, in the PLSVC layer, you will receive some generated procedures to create the entity. For example: Create_Some_Struct_Rec___(rec_ Some_Struct_Rec).action CreateRecord{ initialcheck none; parameter Param1 Structure(SomeStruct);}structure SomeStruct using SomeEntity{ nestedwithcrud { crud = Create; }} Alternatively, you can use a batch request with a Change Set. Please refer to the Batch Requests section in the Technical Documentation for IFS Cloud.
Hi Chamari, According the spec Patch and Delete requests are done against a resource. So there is no meaning in performing an Patch or Delete against an action. Instead try doing a Patch request against the entity set.
Hello Lisa,If you have debugging privileges, could you please enable adding the query parameter "odata-debug=json" to the request? This will allow us to receive a response containing more detailed information about the error.
The issue lies with the filter query you've written. By wrapping the date values with single quotes, they are treated as Strings. If you remove the single quotes from the date values, it should resolve the issue.Only tested this with IFS Cloud but it is same with IFS Cloud and Apps 10 (in the backend). My main concern is whether the #START_OF_THIS_WEEK# placeholder value is replaced by the client before sending the request to the backend. If removing the single quotes still results in an error, please inspect the request made to the backend. It should not contain #START_OF_THIS_WEEK#; instead, it should have the correct date value.
Hi Rolf,@Nils Wendelöv correct me if I am wrong, The date time controller does not support that kind of calculations.
Hi Rolf,Can you explain a bit about the use case? Are you trying to filter out records in Aureana page or is this for an integration?
Hi Ken,There is no access control implemented for excel export. Basically a user can export what he sees in the aurena page.Thank You,Kosala
@CdcJanjaSIt looks like the problem is in where you have included the thirdparty jar. Instead of placeing it in the fndbas\source\fndbas\framework\thirdparty directory, can you try moving it to source\fndbas\projection\lib\{thirdpartyJar.jar} ?Kosala De Silva
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
