https://legacy.forums.gravityhelp.com/topic/post-category-conditional-fields-not-showing-in-notification Gravity Support Forums Topic: Post Category Conditional Fields Not Showing In Notification en-US Tue, 21 Apr 2026 01:13:28 +0000 http://bbpress.org/?v=1.0.1 q https://legacy.forums.gravityhelp.com/search.php https://legacy.forums.gravityhelp.com/topic/post-category-conditional-fields-not-showing-in-notification#post-59054 Tue, 15 May 2012 15:44:37 +0000 Carl Hancock 59054@https://legacy.forums.gravityhelp.com/ <p>I am closing this support forum post as you already have a priority support ticket for this issue. It will be handled via priority support. </p> https://legacy.forums.gravityhelp.com/topic/post-category-conditional-fields-not-showing-in-notification#post-59016 Tue, 15 May 2012 12:59:27 +0000 nkmagik 59016@https://legacy.forums.gravityhelp.com/ <p>I upgraded to the latest version of Gravity Forms, and I am encountering a related issue. </p> <p>Any field that relies upon a conditional Post Category Field is not being stored in the database so I am not seeing the data in either the entries, notifications, or the rg_lead_detail table.</p> <p>The conditional statement works fine for all the other fields except the Post Category Field. </p> https://legacy.forums.gravityhelp.com/topic/post-category-conditional-fields-not-showing-in-notification#post-54374 Thu, 05 Apr 2012 15:04:20 +0000 nkmagik 54374@https://legacy.forums.gravityhelp.com/ <p>I have a form that shows certain field elements based upon a conditional statement from the Post Category Field. The Post Category Field is set to be displayed as checkboxes. </p> <p>The form submits successfully and the data is available in the entries and the post, but the notification e-mail is missing all the fields that has conditional statements attached with the Post Category.</p> <p>I have tested it, and it appears that it other conditional statements work just fine. It is only the conditional statements that are associated with the Post Category that is causing this issue. </p>