Thanks @Michelle Jabanes-Oracle, I have gotten my answer from raising the support case.

@Michelle Jabanes-Oracle Have tried using another browser but the same error occurs however when including the form into a bundle and pushing it to another environment, was able to change ID of the form - really strange indeed 😅

Hi @Michelle Jabanes-Oracle, I don't believe there is restriction on the button as it is a standard feature, is there other way to check ?

Sorry Michelle, my bad I found out that it was previously installed hence received the pop-up messages

Hi Michelle, I have used another browser Firefox however still encountered the same error pop-up message, please advise further. Regards, Darren

Hi Michelle, Yes I have done that. Once you select OK, the message of agree to Terms & Service pops up, any idea to get this agreed or signed ?

Thanks Michelle, I found it but I've got this message, any idea ?

for some reason with custom fields, you can make them mandatory yet make them inlined/disabled via the transaction body fields

awesome thanks michelle, i learnt something new today

As you all can see it is still not working for me PO Form:

i have actually moved the terms to Screen Fields Main, maybe it is to do with my sandbox environment

standard field is "terms"

Yes, the correct form is selected however Inline Text or Disabled selection does not reflect on the purchase order. Perhaps I should also mentioned that this field is pre-populated once the vendor has been selected but I don't think it would be able to affect how the field is displayed

Thanks Michelle, I have made the changes there unfortunately it is not reflecting. The standard field can still be edited. There must be something else that is overriding the Display Type there.

I have tried looking at the transaction body fields for the same functionality (normal, in-line, disabled) but can only find the custom fields listed. Does anyone know where to find this functionality for standard field ?