Issues Disabling Lookup and Number Fields via JavaScript

Forms SharePoint Online
1

Hi everyone,

I'm trying to disable a lookup field and a number field using the following JavaScript code:

javascript

fd.field('{fieldName}').disabled = true;

However, I'm running into issues:

  1. Lookup Field: The UI correctly shows the field as disabled, but the browser's developer console displays an error message.
  2. Number Field: The UI does not disable the field at all, and the browser's developer console also shows an error message.

image

Is there a correct way to disable these types of fields via JavaScript? Any help or suggestions would be greatly appreciated.

Thanks!

2

Hello @Ari_Gunawan ,

you can do a workaround if it throws up errors in console.
Add the ".disabled" class to your element - data field (Looku).

In JS

$(".disabled").prop("disabled",true)

But as I can see in documentation, it should also work with .disabled.

Regards
Stepan

3

Hello @Ari_Gunawan,

Most probably the Lookup field is not fully loaded when the code is executed. Please use this code to disable Lookup field on form load:

fd.field('Field1').ready().then(function(field) {
    fd.field('Field1').disabled = true;
});
4

Thanks @Margo !
You are correct. It might be because the lookup field is not fully loaded under fd.spRendered function.
Your workaround works for Lookup field.

However, the same approach doesn't seem to apply to the Number field.
image

5

@Ari_Gunawan,

ready() function is required only for Lookup and Person or Group fields, Number field should work without it.

6

It works when I disable it on event handler (e.g. on click button).
However, it doesn't work when I disable it on fd.spRendered function:

fd.spRendered(function() {
   if ({some logic}) {
      fd.field('Amount').disabled = true;
   }
});

I got below error message:
image

It looks like the Number field is not fully loaded as well on fd.spRendered function.

7

@Ari_Gunawan,

Is this a complete code you have on the form? Please debug the code and comment out the line with the enable

8

There is no 'enable' in my code—I believe it originates from Plumsail's internal code when my script tries to set .disabled = true, as the error disappeared when I comment out that line.

However, it seems the issue has been resolved. The set disabled functionality is now working as expected, and even the lookup field no longer requires the above workaround. The original code when I posted this question is now functioning correctly.

Thanks!

1 Like