Skip to main content

Hello, 

I have a Custom Entity that has an attribute called SITE. Which is a persistent field.
I have then listed all the values in that entity in a Custom Page.

Data for this is populated from an external source.  

 

But this site is not associated with the actual sites available in the environment. They just appear as text. 
 

  1. Is there a way to link the value in this to actual sites?
  2. Can I set permissions for this Custom page based on the site value? (Users will not see records that are not in the User’s sites)

 

Can this be achieved in IFS without using code?


Thank you!

 

Hi @Kalindu,

 

I’m not sure if the site level access restriction can be done using permission sets.

You could have done such a filter on page designer using Datasource Aggregate Ref using context variable  ‘#USER_DEFAULT_SITE#’  but this is unfortunately not working in IFS Cloud yet. According to the below post, IFS is fixing this in 24R2 for filters and hope it would apply for Datasource Aggregate Refs also.

Filter LOV - Dates - Context Variables | IFS Community

 

As an alternate, you can use a saved search with user default site csv and use as the startup behavior for the page. Steps for this is also mentioned in the above post :)

 

Cheers,

Damith

In terms of the custom attribute itself, it could simply be created as a Referenced Field that’s linked to say company_site_lov. This will record in the entity the actual objkey of the site and therefore will no longer be free text.

 

Making the records on the list only populate for the sites the user has access to is much more complex like Damtih mentioned, you’d have

 

@dsj; I’m not sure IFS is fixing using CSVs in the filter cases from the post you linked, Jonas clearly says they are fixing the now() and date functions in the odata parser, but unclear whether they’re adding CSV support to filter cases :)

In terms of the custom attribute itself, it could simply be created as a Referenced Field that’s linked to say company_site_lov. This will record in the entity the actual objkey of the site and therefore will no longer be free text.

 

Making the records on the list only populate for the sites the user has access to is much more complex like Damtih mentioned, you’d have

 

@dsj; I’m not sure IFS is fixing using CSVs in the filter cases from the post you linked, Jonas clearly says they are fixing the now() and date functions in the odata parser, but unclear whether they’re adding CSV support to filter cases :)

 

@SimonTestard I was hoping for the best since non of the CSVs are working in the odata parser :D 

Hi! 
 Thank you for your replies! 

@dsj Using a saved search is user specific and there’s no way we can get every user to do this, specially in case of having this as a secure way of controlling what they see. :(

 

@SimonTestard 

In terms of the custom attribute itself, it could simply be created as a Referenced Field that’s linked to say company_site_lov. This will record in the entity the actual objkey of the site and therefore will no longer be free text.

I added it as a referenced field and it was no longer free text. But when I clicked on it, it just went to the SITE page without filtering for the site that I clicked on. And it was a site that I was a part of.  Any thoughts on that? 

 

Isn’t there any way to connect these values in Custom Entities to actual objects..? My data has Inventory Parts and some of their values.
Isn’t there a way to build entity references for this to work?


Thank you again for your support!
/Kalindu


NB: ​​​​@dsj, im  a big fan of your blog 😉 Thanks for that!


 

Reply


Terms & ConditionsCookie settings