Hi @mdezzi ,It’s quite interesting how IFS assistants work 😀, The workflow behind editing fields in an assistant involves several HTTP requests, beginning with a POST API call to create a record in a temporary table when a field is first edited. Subsequently, a series of PATCH requests are made to update the initial record created. Each request returns the objkey of the corresponding record in the temporary table. Upon completing the assistant, a separate POST request is sent to a different endpoint, often labeled as "finish" or "create".Usually objkey returned from the previous requests is passed as a parameter in this final request. This objkey serves as a reference to the edited record in the temporary table and ensures that the changes made during the assistant's interaction are properly captured and processed. /Trewon
Hi @mtoca This is not possible, It’s not possible to manipulate response headers of APIs exposed through custom projections. /Trewon
Hi @asjaus ,My guess is that this isn’t listing the elements because the Materialized view ‘Query_Designer_Entities_MV’ isn’t refreshed properly. /Trewon
Hi @Malin Norgren I believe this is not possible, CUD operations are coupled together as one entity action in the entity actions grants page as you have also highlighted. Therefore it’s not possible to revoke or grant a single CUD operation from an entity. instead you can either revoke all CUD operations or grant all CUD operations of a single entity at once. Best way to do is to introduce a new action for the update operation that’s required and then grant that action to the user.Please refer - https://docs.ifs.com/techdocs/23r1/030_administration/010_security/020_permission_sets/023_permission_set_projection_grants/#projection_grants_overview
Hi @romsar ,Currently there is no way of duplicating a custom LU with all of it’s attributes. It only duplicates the LU details. /Trewons
Hi @romsar ,Yes you can have the same model in multiple Custom LUs, but the name of the entity can not be the same. /Trewon
Hi @RikardFredlund ,Could you please have a look at this, I’m not sure if this is the correct channel to share it. /Trewon
Hi @crpgaryw ,You can find information about the sizing guide here - / Trewon
Hi @bhavesh Did you deploy the Entity prior to deploying the Projection ? Could you query the Order_Quotation view and verify that the new column is present in the view. /Trewon
Hi @dsj Please make sure that the ‘SQL_TRACE’ system parameter is on and the ‘DEBUGGER’ System privilege is granted for the service account you are using./Trewon
Hi @ZhanHao ,I believe this is not possible, CUD operations are coupled together as one entity action in the entity actions grants page. Therefore it’s not possible to revoke or grant a single CUD operation from an entity. instead you can either revoke all CUD operations or grant all CUD operations of a single entity at once. Please refer - https://docs.ifs.com/techdocs/23r1/030_administration/010_security/020_permission_sets/023_permission_set_projection_grants/#projection_grants_overview
If you want to add a validation, consider setting up an event that activates when a record is created or updated within the designated entity. Within this event setup, opt to use an event action of either 'Execute Online SQL' or 'Workflow' type. This choice will enable you to incorporate a validation step that assesses the letter case accuracy before the data is stored in the database.Refer https://docs.ifs.com/techdocs/foundation1/040_administration/240_integration/320_events/default.htm/Trewon
This probably is the issue then, instead of manually creating the package, Could you please use the IFS Developer studio to do this, Model an entity in a specific module, Implement the needed actions and then refresh dictionary cache. From the query I see that’s used to populate this LOV, Modeling a package without IFS standards wouldn’t include your package and actions in the LOV./Trewon
Can I know the module that the package that you are deploying belongs to, and is that module active ? If you can send me your DB information I can check why the query doesn’t seem to pick your packages. /Trewon
Hi @Edwards,Have you tried refreshing the dictionary cache, After new methods are deployed into the database please make sure to refresh the dictionary cache as this LOV is populated using the dictionary tables. /Trewon
Hi @rosscortb,IFS API Explorer is available in IFS10 as well, Have you tried searching it in the navigator of the Aurena client ?/Trewon
Hi @JamesW72 ,The SOAP Gateway of IFS Connect serves specifically for integrations, focusing solely on integration endpoints rather than main endpoints. If you require SOAP-based integration endpoints, you can accomplish this through IFS CONNECT./Trewon
Hi @JamesW72 ,IFS OData Provider exposes IFS business entities and business logic through OData endpoints, OData (Open Data Protocol) is a protocol specifically designed for building and consuming RESTful APIs. It does not support SOAP. Thanks, Trewon
Hi @Tom_Lucifer Which version of IFS CLOUD are you using ? /Trewon
Hi Janick,Please refer to the two links below. See if you can find an answer for your issue. Thanks,Trewon Weerasooriya
Hi,In IFS context, when you raise an error (Error_SYS.Record_General) you can only return a single error detail record. However it’s returned as an array through the rest endpoint in order to adhere to OData guidelines . Even though one detail is returned, it should be wrapped in an array to adhere to the OData protocol. Thanks,Trewon Weerasooriya
Hi,By using an array, the API can accommodate multiple details for a single error response, which can be useful in scenarios where there are multiple issues or sub-errors associated with the main error. The array structure provides flexibility for capturing and communicating various error details in a consistent and standardized manner.However using an array for the "details" field aligns with the guidelines and conventions followed in the OData specification, as mentioned in the OData documentation. Adhering to these standards ensures compatibility and consistency across OData-compliant systems and helps facilitate interoperability between different APIs. In summary, the representation of the "details" field as an array in the API documentation is in order to adhere to the OData guidelines for error handling.Thanks,Trewon Weerasooriya
Hi,Please provide a value for the Datasource Entity set. Select the entity set that you wan the list to pull data from. Thank you,Trewon Weerasooriya
Sure, *sent to you directly*
I See that the association is configured using cf_project_id as the parent key, Could you please add it to the group to see if it has data ?
Already have an account? Login
No account yet? Create an account
Enter your 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.
