Considerations and Limitations for Article Personalization for Knowledge and Dynamic Forms

Before enabling Article Personalization, review the considerations and limitations related to Dynamic Forms.

• After you upgrade to Dynamic Forms, the only way to go back to the previous page layout for Knowledge is to drag a new record detail component onto the record page in the Lightning App Builder.
• The File field is not supported on Dynamic Forms.
• If you use Dynamic Forms to set a filter on the Is Primary Language field and a knowledge article is using that primary language, the filter always returns a value of FALSE if the org is not set up for multi-language support.
• A known issue prevents setting the following fields as read-only when using Dynamic Forms, but not when using the page layout:
  • Language (the field is writable only when creating a new knowledge article) Visible in Public Knowledge Base
  • Visible in Partner Portal
  • Visible in Customer Portal
• Page Layout field properties that define whether a field is read-only, required, or neither, are not maintained when upgrading the record page to Dynamic Forms. When you upgrade the record page to Dynamic Forms, you must define the field properties again in the Lightning App Builder.