Hi @Kavinda Hellarawa ,Can you please try the following :1. Check whether the Read Collection and Override ETag are both unchecked inside your Read Element ? We found that updatading a record through BPA Projection Elements require a Read. Probably to get the Etag.2. Inside your Update Projection Element, move the Company and AuthorizerId parameters to the “Nested Entity Parameters”. See the below example where the parent parameters are defined in the Nested Entity parameters. Seems to work correctly. If this does not work, can you try checking the “Upsert” or switching to a Create action and see whether an error is still generated ?Regards,Trishen
@TheoB ,Thank you for sharing this solution. This would certainly be useful as a generic RestAPI.Best Regards,Trishen
Hello @TheoB ,We are currently encountering the same issue. Seems that you can send the stream message only to the person you are authenticated with. Did you find a solution to this ? Regards,Trishen
Hi @jgrace ,Here is what we usually do to create datasources using multiple views.1. Create and deploy an IAL where you'll be placing your SELECT with all the joins required.Path : Solution Manager > Reporting and Analysis > Information Access Layer > IAL Object2. Create a quick information source draft from that IAL.Path : Solution Manager > Reporting and Analysis > Information Sources > Quick Information Sources Drafts > Quick Information Sources3. Create an information source from the drafted quick information source.A view will automatically be created at this point. The view name can be obtained in the “Data Access Type Information” group. Path : Solution Manager > Reporting and Analysis > Information Sources > Information Sources > Information SourceYou will be able to use the view in your datasource.Regards,Trishen
Hello @bdoucette ,You can create an entity association to link 2 different entities.This can be done through a Projection Configuration. Please find an example below where we have a custom entity that we have created linked to the project definition entity. It is important to note that the Key in the child entity needs to be a persistent field and not a referenced field.On your page configuration , you’ill need to add a binding (using the key mapping defined in the projection configuration) in order to get the propoer filtered data. Link to docs : Entity Associations - Technical Documentation For IFS CloudRegards,Trishen
Hi @ChamariJ , As discussed internally with @Asheer the Etag error was actually a bug on our environment (21R1).Upgrading to 22R1 solved the issue. We tested your solution and it works great. Thank you 🙂 Regards,Trishen
Hello @eqbstal , Yes, hardcoding the country code works correcly.We have identified the issue - referenced fields store the objkey of the refence and not the primary key. The BPA was thus trying to parse the OBJKEY inside the Country code. To resolve this issue we have created a read only field in the source entity to store the Country code. We then use this value in BPA as parameter. Regards,Trishen
Hello @ToBeNL , The contents of dropdown lists can be modified through the page designer. Attribute Document No is of type referenced. It should be bound to a selector. For custom fields, this selector is created automatically when you add the field on a page (prefixed with CPEGEN). The contents of the selector can be customised the same way you would customise a list. Results : Regards,Trishen
Hello, The following method worked for me :Refreshing the security and report server cache.Logging out and in againAlso, make sure the lobby is in a permission set assigned to your user. Regards,Trishen
Hi antUdayaP, Thank you for sharing this information.Can you please let me know the your environment version ? It seems that I cannot add custom filters on the datasource attribute. That is the case even if its a static value rather than a parameter. I’m on IFS Cloud 21R1. Kindest regards,Trishen
Hello, Is there a way to replicate this in IFS Cloud ? Saved search is available on LoV lists but how can we use fields on the current screen as parameter ? Regards,Trishen
Hello, I also have the same problem on 21R2.Seems that compared to Apps 10, we cannot define secondary keys in a custom entity (versus a Custom Logical Unit). This would also mean that duplicate records can be created. Feedback on this problem would really be helpful. Regards,Trishen
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.
