Checkboxes

[Filipe Ribeiro]

Hello Alexander

Despite the field returning False, or in this case, returning “Não” correctly, a marked checkbox is incorrectly displayed.

Uploaded picture

Attachments:

1. 

   picturemessage_xysaxxul.bmn_.png
   

[Alexander Bautz]

What is your language / LCID? – I may be missing support for that specific language. Try hitting F12 and type in this and hit Enter:

_spPageContextInfo.currentLanguage

Alexander

[Filipe Ribeiro]

Uploaded printscreen

Attachments:

1. 

   lang_pt-pt.png
   

[Alexander Bautz]

Thanks, I’m missing this LCID in a function that identifies “Yes” and “No” labels for this specific language – can you reply with the correct text for Yes and No so I can add them to the next version?

Alexander

[Filipe Ribeiro]

Yes = Sim
No = Não

[Alexander Bautz]

Thanks, you can fix it by adding this to your Custom JS while waiting for the next version:

spjs.dffs.stringToBoolean = function (lcid, s) {
    var a = {
        "1044": { "Ja": true, "Nei": false },
        "1026": { "Да": true, "Не": false },
        "2052": { "是": true, "否": false },
        "1050": { "Da": true, "Ne": false },
        "1029": { "Ano": true, "Ne": false },
        "1030": { "Ja": true, "Nej": false },
        "1043": { "Ja": true, "Nee": false },
        "1033": { "Yes": true, "No": false },
        "1035": { "Kyllä": true, "Ei": false },
        "1036": { "Oui": true, "Non": false },
        "1031": { "Ja": true, "Nein": false },
        "1032": { "Ναι": true, "Όχι": false },
        "1034": { "Sí": true, "No": false },
        "1038": { "Igen": true, "Nem": false },
        "1040": { "Sì": true, "No": false },
        "1041": { "はい": true, "いいえ": false },
        "1087": { "Иә": true, "Жоқ": false },
        "1042": { "예": true, "아니요": false },
        "1045": { "Tak": true, "Nie": false },
        "1046": { "Sim": true, "Não": false },
        "1048": { "Da": true, "Nu": false },
        "1049": { "Да": true, "Нет": false },
        "1051": { "Áno": true, "Nie": false },
        "1060": { "Da": true, "Ne": false },
        "3082": { "Sí": true, "No": false },
        "1053": { "Ja": true, "Nej": false },
        "1055": { "Evet": true, "Hayır": false },
        "1058": { "Так": true, "Ні": false },
        "2070": { "Sim": true, "Não": false }
    }, r = s;
    if (a[lcid] !== undefined && a[lcid][s] !== undefined) {
        r = a[lcid][s];
    }
    return r;
};

Alexander

[Filipe Ribeiro]

I added that code to the custom JS but rules defined in the past for checkedboxes that activate the visibility of thats still not working.

Uploaded images

Attachments:

1. 

   Capture__dffs_checkboxes_01.png
   

2. 

   Capture__dffs_checkboxes_02.png
   

[Filipe Ribeiro]

@Alexander

Noticied that those rules only stopped validating in DispForm. In EditForm all is good.

[Alexander Bautz]

Are you 100% sure you added it to your DispForm Custom JS?

Alexander

[Filipe Ribeiro]

Yes did exactly on DispForm anyother consideration to fix this?

[Alexander Bautz]

I have found a problem with the boolean slider implementation that caused this DispForm issues and will fix it in the next release.

Alexander

[Filipe Ribeiro]

@Alexander we’ve found another problem caused by the non support the language (pt-PT), can you help us

uploaded image

Attachments:

1. 

   Capture_groupby_01.png
   

[Alexander Bautz]

This grouping function doesn’t use the same method so the value is either true or false if you group on a boolean field. My suggestion is to create a calculated field you can use here.

Alexander

[Filipe Ribeiro]

Hello

Not sure if I fully understood the alternative for what we have today. Can you clarify with an example?

[Alexander Bautz]

I meant to create a new calculated field in the list where you use a formula like this:

=IF([name_of_your_boolean_field]=TRUE,"Yes","No")

Now you can use this field in the GroupBy FieldInternalName to show “Yes” and “No” instead of true and false.

Alexander

[Filipe Ribeiro]

Hi Alexander

It worked! Thank you.

But we’re still having issues with the missing support for pt-PT, any thoughts when youre going to release a new version containing that support?

[Alexander Bautz]

This error is not related to pt-PT only, but is a general issue with getFieldValue on a boolean field in DispForm.

I’m working on it, but there are a lot of other changes in this version so It must be posted as a BETA first – hopefully tomorrow or Friday.

You can downgrade to DFFS v4.4.4.25 (March 14, 2020) – and add the override to the stringToBoolean function in DispForm and it should work.

Alexander

[Filipe Ribeiro]

Looking forward for an update version

[Filipe Ribeiro]

Hi Alexander

We’ve updated the development environment with the newest DFFS version (BETA, ATM) and we are running into some issues. It’s not recognizing the values 0/1 as true/false. Upçloaded image

Attachments:

1. 

   DFFS_BETA_DEV.jpg
   

[Alexander Bautz]

Are you sure this field is actually added to all content types in this list? – go into the list settings and click the content type you are using and see if you can find the field there.

Alexander

[Filipe Ribeiro]

Uploaded images. The field already created, long time ago, how can we be sure if it was checked the option do add to all content types?

Attachments:

1. 

   image_2020_05_27T13_37_37_730Z.png
   

2. 

   image_2020_05_27T13_42_56_086Z.png
   

[Alexander Bautz]

Impossible to tell, but just scroll up the page, click the “Tarefa” content type, scroll down and select “Add from existing site or list columns” and add it to the content type.

Alexander

[Filipe Ribeiro]

Hi Alexander

Sorry for the wrong info. We had de DFFS v4.4.4.17 and upgraded to DFFS v4.4.4.25 (March 14, 2020) not the BETA

[Filipe Ribeiro]

After the update to DFFS v4.4.4.25 (March 14, 2020) the results were the ones I reported before

Summing up, fields that weren’t associated to a content type are returning errors and in last version we haed (.17) everything was ok except pt-PT support

Will BETA fix this?

Attachments:

1. 

   DFF_25_lookup-1.jpg
   

[Alexander Bautz]

The message telling that the field is not in the content type has been added after v4.4.4.17, but it was done to alert you about a field that is inserted in a tab, but cannot possibly be shown because it is not in the content type currently used in the form.

Do you have a form configured where the field is visible in the tab in one content type and not in another – and you want the field to just not render if it is not in the content type?

Alexander

[Filipe Ribeiro]

Upload new prints

Fields, internally created from the lookup are returning that error when used in tab

Attachments:

1. 

   lookup-error_content_type_setting.png
   

2. 

   lookup-error_content_type.png
   

3. 

   lookup-error_content_type_tab.png
   

[Alexander Bautz]

I see. I cannot control how SharePoint handles adding the fields to all content types when creating “additional fields” from a lookup column, but I could of course remove the “warning” about the field not being in the content type, but it would not make the field visible – removing the warning would just make it harder to figure out why the field does not show.

Is the problem that you don’t want the fields added to the content type and just want the error to go away (but still not see the fields)?

Alexander

[DevAmb]

We manage to resolve our problem. thank you for the help.

[Author]

Posts