how to activate the attachment encryption for both parent and child tablesSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } In ServiceNow, Encrypted Field Configuration (EFC) for Attachment types does not inherit from a parent table to its child tables. This means that if your data model includes both a parent table and one or more child tables, you must configure attachment encryption separately for each table. However, due to the known defect PRB1873195, users on the Yokohama release are unable to activate attachment-level EFC on both the parent and child tables at the same time. When attempting to enable encrypted attachments on multiple related tables, the platform blocks the second configuration due to an erroneous validation introduced by the defect. For customers who must enable encrypted attachments on both a parent table and its child table and cannot yet upgrade to the Zurich release (where the issue is fixed), the following workaround can be applied using a background script. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Yokohama Instructions<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } There are two safe methods customers can use until they can upgrade to Zurich. Prerequisites Admin-level accessAbility to run scripts in Background ScriptsUnderstanding of table names and sys_ids for the relevant EFC records Workaround Option 1: Create the EFC Record Directly Using a Background Script Use this method when you need to create a new attachment encryption configuration for a specific table. Steps Navigate to System Definition → Scripts - Background.Run the following script after replacing the xxx placeholder with the actual table name. var g = new GlideRecord("sys_platform_encryption_configuration"); g.initialize(); g.setValue('table', 'xxx'); // replace xxx with table name g.setValue('type', 'Attachment'); g.setValue('method', "multikmfmodule"); g.setWorkflow(false); // disable business rules g.insert(); What This Does Creates a new EFC recordAssigns type = AttachmentAssigns the correct encryption methodDisables the business rules that normally block the configuration due to the defect Workaround Option 2: Create EFC from the UI, Then Update via Script Use this method if a customer prefers to use the UI for initial creation. Steps Via the UI, create any Attachment-type EFC on any table (a random test table is acceptable).Locate the newly created record and copy its sys_id.Navigate to System Definition → Scripts - Background.Run the following script, replacing: "XXXXX" with the sys_id of the newly created EFC'xxx' with the intended target table var g = new GlideRecord("sys_platform_encryption_configuration"); g.get("XXXXX"); // specify sys_id of EFC created on random table g.setValue('table', 'xxx'); // replace xxx with table name g.setWorkflow(false); // disable business rules g.update(); What This Does Updates the existing UI-created EFCReassigns it to the correct parent or child tableBypasses the blocking business rule generated by PRB1873195