https://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-recorden-USTelligent Community 12https://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-recordWed, 15 Dec 2021 02:45:50 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b0682487-f56c-44ed-81ed-5836d6dfb957Parmida Borhanihttps://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record#commentsCurrent Revision posted to Appian Knowledge Base by Parmida Borhani on 12/15/2021 2:45:50 AM<br /> <h2><span>Symptoms</span></h2> <p><span>When loading a record type, the error <code>The field [fieldName] does not exist</code> appears.</span></p> <p><span><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-11/8228.DEV-env-_2D00_-Record-error-message-_2800_1_2900_.png" /></span></p> <p><span>Other details:</span></p> <ul> <li><span>This error may not have appeared previously for the same record type.</span></li> <li><span>This error may not appear for a record type with the same configuration in another environment.</span></li> </ul> <h2><span>Cause</span></h2> <p><span>When a record type is registered, the&nbsp;rf! variables may become case sensitive and must match the casing in the related custom data type. Record types are registered during environment restarts and record type deployments.&nbsp;</span>This issue has been reported to the Appian Product Team. The reference number for this issue is <strong>AN-185807</strong>.</p> <h2><span>Workaround</span></h2> <p><span>Apply either of the following changes to the affected record type:</span></p> <ul> <li>Update the casing of all references fields using rf! to match the casing in the custom data type.</li> <li><a style="font-family:inherit;" href="https://docs.appian.com/suite/help/latest/update-a-record-type.html">Update the legacy record type</a><span style="font-family:inherit;"> to a modern record.</span></li> </ul> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian using legacy record types.</span></p> <p><span>Last Reviewed: December 2021</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, record type, application design, open issues</div> https://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record/revision/7Wed, 15 Dec 2021 02:45:50 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b0682487-f56c-44ed-81ed-5836d6dfb957Parmida Borhanihttps://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record#commentsRevision 7 posted to Appian Knowledge Base by Parmida Borhani on 12/15/2021 2:45:50 AM<br /> <h2><span>Symptoms</span></h2> <p><span>When loading a record type, the error <code>The field [fieldName] does not exist</code> appears.</span></p> <p><span><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-13/8228.DEV-env-_2D00_-Record-error-message-_2800_1_2900_.png" /></span></p> <p><span>Other details:</span></p> <ul> <li><span>This error may not have appeared previously for the same record type.</span></li> <li><span>This error may not appear for a record type with the same configuration in another environment.</span></li> </ul> <h2><span>Cause</span></h2> <p><span>When a record type is registered, the&nbsp;rf! variables may become case sensitive and must match the casing in the related custom data type. Record types are registered during environment restarts and record type deployments.&nbsp;</span>This issue has been reported to the Appian Product Team. The reference number for this issue is <strong>AN-185807</strong>.</p> <h2><span>Workaround</span></h2> <p><span>Apply either of the following changes to the affected record type:</span></p> <ul> <li>Update the casing of all references fields using rf! to match the casing in the custom data type.</li> <li><a style="font-family:inherit;" href="https://docs.appian.com/suite/help/latest/update-a-record-type.html">Update the legacy record type</a><span style="font-family:inherit;"> to a modern record.</span></li> </ul> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian using legacy record types.</span></p> <p><span>Last Reviewed: December 2021</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, record type, application design, open issues</div> https://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record/revision/6Tue, 09 Nov 2021 06:02:10 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b0682487-f56c-44ed-81ed-5836d6dfb957Tom Ryanhttps://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record#commentsRevision 6 posted to Appian Knowledge Base by Tom Ryan on 11/9/2021 6:02:10 AM<br /> <h2><span>Symptoms</span></h2> <p><span>When loading a record type, the error <code>The field [fieldName] does not exist</code> appears.</span></p> <p><span><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-13/8228.DEV-env-_2D00_-Record-error-message-_2800_1_2900_.png" /></span></p> <p><span>Other details:</span></p> <ul> <li><span>This error may not have appeared previously for the same record type.</span></li> <li><span>This error may not appear for a record type with the same configuration in another environment.</span></li> </ul> <h2><span>Cause</span></h2> <p><span>When a record type is registered the&nbsp;rf! variables may become case sensitive and must match the casing in the related custom data type. Record types are registered during environment restarts and record type deployments.&nbsp;</span>This issue has been reported to the Appian Product Team. The reference number for this issue is <strong>AN-185807</strong>.</p> <h2><span>Workaround</span></h2> <p><span>Apply either of the following changes to the affected record type:</span></p> <ul> <li>Update the casing of all references fields using rf! to match the casing in the custom data type.</li> <li><a style="font-family:inherit;" href="https://docs.appian.com/suite/help/latest/update-a-record-type.html">Update the legacy record type</a><span style="font-family:inherit;"> to a modern record.</span></li> </ul> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian using legacy record types.</span></p> <p><span>Last Reviewed: October 2021</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, record type, application design, open issues</div> https://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record/revision/5Mon, 08 Nov 2021 13:42:20 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b0682487-f56c-44ed-81ed-5836d6dfb957Zach Puderbachhttps://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record#commentsRevision 5 posted to Appian Knowledge Base by Zach Puderbach on 11/8/2021 1:42:20 PM<br /> <h2><span>Symptoms</span></h2> <p><span>When loading a record type, the error <code>The field [fieldName] does not exist</code> appears.</span></p> <p><span><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-13/8228.DEV-env-_2D00_-Record-error-message-_2800_1_2900_.png" /></span></p> <p><span>Other details:</span></p> <ul> <li><span>This error may not have appeared previously for the same record type.</span></li> <li><span>This error may not appear for a record type with the same configuration in another environment.</span></li> </ul> <h2><span>Cause</span></h2> <p><span>Intermittently, when a record type is registered the&nbsp;rf! variables become case sensitive and must match the casing in the related custom data type. Instances a record type would be registered include environment restart and record type deployment.&nbsp;</span>This issue has been reported to the Appian Product Team. The reference number for this issue is <strong>AN-185807</strong>.</p> <h2><span>Workaround</span></h2> <p><span>Apply either of the following changes to the affected record type:</span></p> <ul> <li>Update the casing of all references fields using rf! to match the casing in the custom data type.</li> <li><a style="font-family:inherit;" href="https://docs.appian.com/suite/help/latest/update-a-record-type.html">Update the legacy record type</a><span style="font-family:inherit;"> to a modern record.</span></li> </ul> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian using legacy record types.</span></p> <p><span>Last Reviewed: October 2021</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, record type, application design, open issues</div> https://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record/revision/4Wed, 03 Nov 2021 17:29:17 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b0682487-f56c-44ed-81ed-5836d6dfb957Zach Puderbachhttps://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record#commentsRevision 4 posted to Appian Knowledge Base by Zach Puderbach on 11/3/2021 5:29:17 PM<br /> <h2><span>Symptoms</span></h2> <p><span>When loading a record type, the error <code>The field [fieldName] does not exist</code> appears.</span></p> <p><span><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-13/8228.DEV-env-_2D00_-Record-error-message-_2800_1_2900_.png" /></span></p> <p><span>Other details:</span></p> <ul> <li><span>This error may not have appeared previously for the same record type.</span></li> <li><span>This error may not appear for a record type with the same configuration in another environment.</span></li> </ul> <h2><span>Cause</span></h2> <p><span>Intermittently, when a record type is registered, such as on environment restart or record type deployment, the&nbsp;rf! variables become case sensitive and must match the casing in the related custom data type.&nbsp;</span>This issue has been reported to the Appian Product Team. The reference number for this issue is <strong>AN-185807</strong>.</p> <h2><span>Workaround</span></h2> <p><span>Apply either of the following changes to the affected record type:</span></p> <ul> <li>Update the casing of all references fields using rf! to match the casing in the custom data type.</li> <li><a style="font-family:inherit;" href="https://docs.appian.com/suite/help/latest/update-a-record-type.html">Update the legacy record type</a><span style="font-family:inherit;"> to a modern record.</span></li> </ul> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian using legacy record types.</span></p> <p><span>Last Reviewed: October 2021</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, record type, application design, open issues</div> https://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record/revision/3Fri, 22 Oct 2021 18:09:23 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b0682487-f56c-44ed-81ed-5836d6dfb957Zach Puderbachhttps://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record#commentsRevision 3 posted to Appian Knowledge Base by Zach Puderbach on 10/22/2021 6:09:23 PM<br /> <h2><span>Symptoms</span></h2> <p><span>When loading a record type, the error <code>The field [fieldName] does not exist</code> appears.</span></p> <p><span><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-13/8228.DEV-env-_2D00_-Record-error-message-_2800_1_2900_.png" /></span></p> <p><span>Other details:</span></p> <ul> <li><span>This error may not have appeared previously for the same record type</span></li> <li><span>This error may not appear for a record type with the same configuration in another environment.</span></li> </ul> <h2><span>Cause</span></h2> <p><span>Intermittently, when a record type is registered, such as on environment restart or record type deployment, the&nbsp;rf! variables become case sensitive and must match the casing in the related custom data type.&nbsp;</span>This issue has been reported to the Appian Product Team. The reference number for this issue is <strong>AN-185807</strong>.</p> <h2><span>Workaround</span></h2> <p><span>Apply either of the following changes to the affected record type:</span></p> <ul> <li>Update the casing of all references fields using rf! to match the casing in the custom data type.</li> <li><a style="font-family:inherit;" href="https://docs.appian.com/suite/help/latest/update-a-record-type.html">Update the legacy record type</a><span style="font-family:inherit;"> to a modern record.</span></li> </ul> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian using legacy record types.</span></p> <p><span>Last Reviewed: October 2021</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, record type, application design, open issues</div> https://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record/revision/2Fri, 22 Oct 2021 18:03:34 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b0682487-f56c-44ed-81ed-5836d6dfb957Zach Puderbachhttps://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record#commentsRevision 2 posted to Appian Knowledge Base by Zach Puderbach on 10/22/2021 6:03:34 PM<br /> <h2><span>Symptoms</span></h2> <p><span>When loading a record type, the error &quot;The field [fieldName] does not exist&quot; appears.</span></p> <p><span><img alt=" " border="0" src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-00-13/DEV-env-_2D00_-Record-error-message-_2800_1_2900_.png" /></span></p> <p><span>Other details:</span></p> <ul> <li><span>This error may not have appeared previously for the same record type</span></li> <li><span>This error may not appear for a record type with the same configuration in another environment.</span></li> </ul> <h2><span>Cause</span></h2> <p><span>Intermittently, when a record type is registered, such as on environment restart or record type deployment, the&nbsp;rf! variables become case sensitive and must match the casing in the related custom data type.&nbsp;</span>This issue has been reported to the Appian Product Team. The reference number for this issue is <strong>AN-185807</strong>.</p> <h2><span>Workaround</span></h2> <p><span>Apply either of the following changes to the affected record type:</span></p> <ul> <li>Update the casing of all references fields using rf! to match the casing in the custom data type.</li> <li><a style="font-family:inherit;" href="https://docs.appian.com/suite/help/latest/update-a-record-type.html">Update the legacy record type</a><span style="font-family:inherit;"> to a modern record.</span></li> </ul> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian using legacy record types.</span></p> <p><span>Last Reviewed: October 2021</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, record type, application design, open issues</div> https://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record/revision/1Fri, 22 Oct 2021 17:42:41 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b0682487-f56c-44ed-81ed-5836d6dfb957Zach Puderbachhttps://community.appian.com/support/w/kb/2487/kb-2205-the-field-fieldname-does-not-exist-error-thrown-when-loading-a-record#commentsRevision 1 posted to Appian Knowledge Base by Zach Puderbach on 10/22/2021 5:42:41 PM<br /> <h2><span>Symptoms</span></h2> <p><span>When loading a record type, the error &quot;The field [fieldName] does not exist&quot; appears.</span></p> <p><span>Other details:</span></p> <ul> <li><span>This error may not have appeared previously for the same record type</span></li> <li><span>This error may not appear for a record type with the same configuration in another environment.</span></li> </ul> <h2><span>Cause</span></h2> <p><span>Intermittently, when a record type is registered, such as on environment restart or record type deployment, the&nbsp;rf! variables become case sensitive and must match the casing in the related custom data type.&nbsp;</span>This issue has been reported to the Appian Product Team. The reference number for this issue is <strong>AN-185807</strong>.</p> <h2><span>Workaround</span></h2> <p><span>Apply either of the following changes to the affected record type:</span></p> <ul> <li>Update the casing of all references fields using rf! to match the casing in the custom data type.</li> <li><a style="font-family:inherit;" href="https://docs.appian.com/suite/help/latest/update-a-record-type.html">Update the legacy record type</a><span style="font-family:inherit;"> to a modern record.</span></li> </ul> <h2><span>Affected Versions</span></h2> <p><span>This article applies to all versions of Appian using legacy record types.</span></p> <p><span>Last Reviewed: October 2021</span></p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: known issues, record type, application design, open issues</div>