# Why does attributes set in JDBC modify account provisioning policy not come up in provisioining plan in IDN **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** provisioning, identity-security-cloud\ **Created:** [May 7, 2024, 1:12pm UTC](https://developer.sailpoint.com/discuss/t/why-does-attributes-set-in-jdbc-modify-account-provisioning-policy-not-come-up-in-provisioining-plan-in-idn/55716 "2024-05-07T13:12:11Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![jesvin90](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jesvin90/32/5301_2.png) [@jesvin90](https://developer.sailpoint.com/discuss/u/jesvin90)\ **Post date:** [May 7, 2024, 2:30pm UTC](https://developer.sailpoint.com/discuss/t/why-does-attributes-set-in-jdbc-modify-account-provisioning-policy-not-come-up-in-provisioining-plan-in-idn/55716/5 "2024-05-07T14:30:55Z")
Hi @RohanBhat10, You will need to rely on a before provisioning rule to pass the attributes. Take a look at the below blog post : > [@Pass Non-Provisioned Attributes from Before Provision rule to Connector Rules](https://developer.sailpoint.com/discuss/t/pass-non-provisioned-attributes-from-before-provision-rule-to-connector-rules/20470): > > Introduction A common use case when developing for provisioning is the need to provide information to a connector rule that is not available on the virtual appliance (VA). This can occur because you need identity information to perform additional logic, or because a request payload requires information that is not actively changing in the account. The first case can often occur in Active Directory and Azure Native Rules, where a developer must take additional actions based on… --- _[View the full topic](https://developer.sailpoint.com/discuss/t/why-does-attributes-set-in-jdbc-modify-account-provisioning-policy-not-come-up-in-provisioining-plan-in-idn/55716)._