Rule issue with multiple content types

[Leonid]

I have a SP list with multiple content types.
Several content types have a Person field “TrainingCoordinator” and some don’t. The form has a Rule that checks peoplepicker for that field. When the EDIT form comes up for a content type which doesn’t have “TrainingCoordinator” field, DFFS throws an error attached. Even with linked rule defined to check for the content type, error still thrown. The EDIT form works fine when called on other content types.

Attachments:

1. 

   TC.jpg
   

[Leonid]

Seems its a specific bug. When this error occurs, it prevents cascading dropdowns render

• This reply was modified 5 years, 1 month ago by Leonid.

[Alexander Bautz]

Hi,
When you use content types you will have to create rules that only triggers if you have a specific content type.

I suggest adding a rule in the top of the rules section for each of the content types and have them trigger on “Content type = your content type”. These rules does not have to do anything, but you can use them in the “Linked rules and functions” in your other rule to ensure it only triggers if the correct content type is detected.

I generally don’t recommend using content types with DFFS – you can create the different form layouts using rules and tabs in DFFS to mimic the functionality.

Alexander

[Leonid]

Alex,
That’s pretty much what I’ve tried. Yet, Even when the rule is NOT a match, DFFS error still thrown as if the rule is processed. Here’re snapshots

Attachments:

1. 

   RULE_CT.jpg
   

2. 

   RULE_CHOICE.jpg
   

3. 

   TR_LOGIN.jpg
   

4. 

   TR_DEBUG.jpg
   

[Alexander Bautz]

OK, it seems the function that tries to validate the people picker fails when the field is not in the content type. You need to make some changes and create two rules like the attached images, and then one function in Custom JS like this:

function isCorrectCT_setPeoplePicker(){
    var isTC = spjs.dffs.beforeProperties.TrainingCoordinator_ID[0] === String(_spPageContextInfo.userId);
    if(isTC){
        spjs.dffs.triggerRule(["isTC_CallFromCustomJS"]);
    }
}

Please note that you should NOT use quotes around the content type names in the rule trigger “This value” field.

Let me know how this works out.

Alexander

Attachments:

1. 

   CT_Trigger_1.png
   

2. 

   CT_Trigger_2.png
   

[Leonid]

Thanks Alex,
In my scenario the rule checks if current user is the one in peoplepicker. That’s where the error happens. Do I understand correctly that I cant use the rule trigger for that and have to use javascript function to compare current user with peoplepicker?

The preferred solution would be to allow rules on every field present in list definition regardless of which content type it belongs to.

[Alexander Bautz]

You can use the workaround I suggested, but I’ll look into changing it so it will not throw this error, just return false if the field it not present.

Alexander

[Leonid]

Awesome, Alex, thanks!
BTW,

spjs.dffs.beforeProperties

is a hidden gem!

[Leonid]

To close this topic, is there DFFS syntax to add actual field control programmatically?
I understand that control’s values can be added as {<control_name>} and {{<control_name>}}. Say if my control is a choice dropdown, is there a way to add it vs writing the whole HTML?

[Alexander Bautz]

No, DFFS does not insert these controls, it overlays the default form and uses the already available controls.

Alexander

[Leonid]

Alex, another test run negative with Content Type edit form. The field defined in current CT still doesnt show, nor das a row with variable linked to the field. Please advice

• This reply was modified 5 years ago by Leonid.

Attachments:

1. 

   TR.jpg
   

2. 

   TR2.jpg
   

3. 

   TR-1.jpg
   

[Leonid]

Never mind, found an problem with reversing rules…

[Author]

Posts