Dear Mohamed,

You have chosen a correct article to implement such functionality. You need to apply filtration for the Contact lookup field. The filter for filter group should be referring SysAdminUnit table and check whether contact has system administrator role. You can evaluate by system administrator role Id. 

Regrads,

Anastasia

Anastasia Botezat writes:

You need to apply filtration for the Contact lookup field. The filter for filter group should be referring SysAdminUnit table and check whether contact has system administrator role. You can evaluate by system administrator role Id. 

That's exactly what I did. But the SysAdminUnit table doesn't have RoleId column.

I looked into SysUserInRole table that contains SysRoleId and SysUserId columns, but I couldn't use it in the filter group.

Do you have any idea how to implement it?

Thank you

Mohamed

Mohamed,

Thank you for the explanation, now I see what you are referring to. The table, which contains the pair contact - role is SysAdminUnitInRole. There are stored pairs SysAdminUnitId and SysAdminUnitRoleId. Both are Ids from SysAdminUnit table.

Regards,

Anastasia

Anastasia Botezat,

Yes. I have to join the Contact, SysAdminUnit, and SysAdminUnitInRole to get the list of Administrators.

In SQL it looks like this:

select * from Contact 
left join SysAdminUnit on Contact.Id = SysAdminUnit.ContactId
left join SysAdminUnitInRole on SysAdminUnit.Id = SysAdminUnitInRole.SysAdminUnitId
where SysAdminUnitRoleId = 
'83A43EBC-F36B-1410-298D-001E8C82BCAD' 
-- sys administrators role id

 How can I use it in filters?

Thank you

Mohamed

Mohamed Ouederni,

Please check the following article on how to build path to the columns:

https://academy.bpmonline.com/documents/technic-sdk/7-14/root-schema-building-paths-columns

The path should be somewhat like this, and be evaluated to the role Id.

Contact.[SysAdminUnit:Contact].[SysAdminUnitInRole:SysAdminUnit].Role

Please use the article and example to build needed path.

Anastasia

Anastasia Botezat,

Thank you. That helps a lot.

For anyone interested in the solution.

filterGroup.add("IsAdmin",
Terrasoft.createColumnFilterWithParameter(
	Terrasoft.ComparisonType.EQUAL,
	"[SysAdminUnit:Contact].[SysAdminUnitInRole:SysAdminUnit].SysAdminUnitRoleId",
	"83A43EBC-F36B-1410-298D-001E8C82BCAD"));

Dear Ayman,

You can add a fixed filter to the lookup page, however, this requires development skills. Please see this article with instructions: 

https://academy.bpmonline.com/documents/technic-sdk/7-13/adding-quick-filter-block-section

The schema you would need to modify is LookupPageViewGenerator. Please note, that applied changes would be displayed for all sections and each place where you use lookup page.

In order to remove New button, you need to override the getSelectionControlsConfig and getEditionControlsConfig methods on LookupPageViewGenerator schema and remove add button from there.

As an alternative approach, you can apply business rule on the field and in this case lookup would be automatically filtered. 

Regards,

Anastasia

Hi Anastasia,

I can't create "replacing client module" with parent is LookupPageViewGenerator. How can I "modify" it as you said? I found lookup Brand and Category in ProductPageV2 which hide button "New" when open its lookup modal. How can I see their source code?

Thanks

Anastasia Botezat,

Please help

Toan Mai,

Hello!



If you want to hide 'NEW' button you can simply add  "hideActions": true to your lookuplistconfig property of the attribute correspondent to lookup field.



Please see snippet below:

define("OrderPageV2", [], function() {
	return {
		entitySchemaName: "Order",
		attributes: {
			"Opportunity": {
				"lookupListConfig": {
					"hideActions": true
				}
			}
		},
		modules: /**SCHEMA_MODULES*/{}/**SCHEMA_MODULES*/,
		details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,
		businessRules: /**SCHEMA_BUSINESS_RULES*/{}/**SCHEMA_BUSINESS_RULES*/,
		methods: {},
		dataModels: /**SCHEMA_DATA_MODELS*/{}/**SCHEMA_DATA_MODELS*/,
		diff: /**SCHEMA_DIFF*/[]/**SCHEMA_DIFF*/
	};
});

It will however also hide actions drop down, but this drop down is also connected to crud operations within lookup field.



See result here:

https://prnt.sc/px04je

Dmytro Smishchenko,

This solution seems to work on lookup object in Order section. How can we implement the same on the Detail ?

hi ayman ,  can you send me code for this model box

Just found the solution to this problem in the following thread:

https://community.bpmonline.com/questions/lookup-field-filter

Javier Collazo,

You can also take a look at this chunk of code, it also represents the combination of two filter groups. The idea is to make firstly one filter group for OR clause. Afterwards, you create a second filter group, which combines a first one OR and other clause. By default filters are added via AND.

getCurrentUserAndTypesFilter: function() {

   var filterGroup = new this.Terrasoft.createFilterGroup();

   filterGroup.logicalOperation = this.Terrasoft.LogicalOperatorType.OR;

   var innerFilterGroupCreatedBy = new this.Terrasoft.createFilterGroup();

   innerFilterGroupCreatedBy.add("CurrentUser", this.Terrasoft.createColumnFilterWithParameter(

      this.Terrasoft.ComparisonType.EQUAL, "Tag.CreatedBy",this.Terrasoft.SysValue.CURRENT_USER_CONTACT.value));

   innerFilterGroupCreatedBy.add("PrivateType", this.Terrasoft.createColumnFilterWithParameter(

      this.Terrasoft.ComparisonType.EQUAL, "Tag.Type", TagConstants.TagType.Private));

   var innerFilterGroupOtherTypes = new this.Terrasoft.createFilterGroup();

   var types = [TagConstants.TagType.Corporate, TagConstants.TagType.Public];

   innerFilterGroupOtherTypes.add("OtherTypes",this.Terrasoft.createColumnInFilterWithParameters(

      "Tag.Type", types));

   filterGroup.addItem(innerFilterGroupCreatedBy);

   filterGroup.addItem(innerFilterGroupOtherTypes);

   return filterGroup;

},

Regards,

Anastasia

Hello,

You need to create a filter group and set OR logical operator.

Please, see my example:



var filterGroup = this.Terrasoft.createFilterGroup();

filterGroup.logicalOperation = this.Terrasoft.LogicalOperatorType.OR;

filterGroup.add("MotherboardsFilter", this.Terrasoft.createColumnFilterWithParameter(

                    this.Terrasoft.ComparisonType.EQUAL,

                     "Name", "Motherboards");

filterGroup.add("GraphicsFilter", this.Terrasoft.createColumnFilterWithParameter(

                    this.Terrasoft.ComparisonType.EQUAL,

                     "Name", "Graphics");

filterGroup.add("MouseFilter", this.Terrasoft.createColumnFilterWithParameter(

                    this.Terrasoft.ComparisonType.EQUAL,

                     "Name", "Mouse");  



You can find more examples in the documentation - https://academy.bpmonline.com/documents/technic-sdk/7-12/entityschemaqu…

Dear Fulgen,

Please see the example below:

// Action handler method. Opens the [Contacts] lookup.
	setOwner: function() {
	// Defining the lookup configuration.
		var config = {
		  // The [Contact] Schema.
		  entitySchemaName: "Contact",
		  // Multiple selection is disabled.
		  multiSelect: false,
		  // The displayed column — [Name].
		  columns: ["Name"]
	     };
	     var EmployeeFilter = 
         this.Terrasoft.createColumnFilterWithParameter(Terrasoft.ComparisonType.EQUAL, "Type.Name",
		 "Employee");
		 EmployeeFilter.Name = "existsFilter";
		 config.filters = EmployeeFilter;
// Opening of the lookup with certain configuration and call-back function that is triggered
// after you click [Select].
		 this.openLookup(config, this.lookupCallback, this);
	},

Hope you will find it helpful.

Regards,

Anastasia

Anastasia Botezat,

Good Day Anastasia,

What does parameters "Type.Name" and Employee represents?



I want my look up to like this one (please see image below).

Default filter - "Category"

Default filter value - "Hardware";

Thanks

Dear Fulgen,

Base on my example, the "Type.Name" and Employee says, that filter will display contacts, whose type is Employee. You can adjust the filter up to your needs.

Regards,

Anastasia