# Custom Session Props in Master do not propagate to Slave **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [January 4, 2024, 3:39pm UTC](https://forum.inductiveautomation.com/t/custom-session-props-in-master-do-not-propagate-to-slave/83792 "2024-01-04T15:39:37Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![ian.sebryk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ian.sebryk/32/49319_2.png) [@ian.sebryk](https://forum.inductiveautomation.com/u/ian.sebryk)\ **Post date:** [January 4, 2024, 3:39pm UTC](https://forum.inductiveautomation.com/t/custom-session-props-in-master-do-not-propagate-to-slave/83792/1 "2024-01-04T15:39:38Z")
Title pretty much says it all. I have a Master project with several custom session props and they do not appear to propagate to the Slave. 🙀 Custom **component** props **do** propagate, but not session ones. I can _export_ session props (which include the custom ones) _to_ the Slave, but that's extra steps that should be unnecessary. Is there something i'm missing here? This seems a major thing that should just be there. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 4, 2024, 3:51pm UTC](https://forum.inductiveautomation.com/t/custom-session-props-in-master-do-not-propagate-to-slave/83792/2 "2024-01-04T15:51:15Z")
Pretty sure that is one of those "all or nothing" inheritance items. (True for their Vision analog, too--Vision Client Tags.) ---
**Author:** ![ian.sebryk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ian.sebryk/32/49319_2.png) [@ian.sebryk](https://forum.inductiveautomation.com/u/ian.sebryk)\ **Post date:** [January 4, 2024, 4:22pm UTC](https://forum.inductiveautomation.com/t/custom-session-props-in-master-do-not-propagate-to-slave/83792/3 "2024-01-04T16:22:22Z")
so this IS a thing!? 😱 i thought i was just missing a setting... how can you expect a Master to BE a Master if a chunk of it's major properties DO NOT PROPAGATE? ![exasperated](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/b/3b288e56e27b50f149a49c8661c0b6d8f7bee740.jpeg) but if it's a thing, it's a thing... just have to adapt. 🍴 ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 4, 2024, 4:29pm UTC](https://forum.inductiveautomation.com/t/custom-session-props-in-master-do-not-propagate-to-slave/83792/4 "2024-01-04T16:29:56Z")
Yes, this is a thing. Inheritance is by project resource, and some project resources contain multiple items. Just as project library scripts inherit or override as a whole, not function by function. The other major case to watch out for is project events. ---
**Author:** ![ian.sebryk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ian.sebryk/32/49319_2.png) [@ian.sebryk](https://forum.inductiveautomation.com/u/ian.sebryk)\ **Post date:** [January 4, 2024, 4:40pm UTC](https://forum.inductiveautomation.com/t/custom-session-props-in-master-do-not-propagate-to-slave/83792/5 "2024-01-04T16:40:14Z")
> [@pturmel](#): > > The other major case to watch out for is project events. 😭 thanks for the heads-up...srsly. 👍 ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 4, 2024, 4:53pm UTC](https://forum.inductiveautomation.com/t/custom-session-props-in-master-do-not-propagate-to-slave/83792/6 "2024-01-04T16:53:02Z")
> [@ian.sebryk](#): > > thanks for the heads-up It's **one** of the reasons I make all events one-liners, delegating to a project script function. ---
**Author:** ![ian.sebryk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ian.sebryk/32/49319_2.png) [@ian.sebryk](https://forum.inductiveautomation.com/u/ian.sebryk)\ **Post date:** [January 4, 2024, 5:16pm UTC](https://forum.inductiveautomation.com/t/custom-session-props-in-master-do-not-propagate-to-slave/83792/7 "2024-01-04T17:16:37Z")
i have much to learn here. i'm coming back to Ignition full force now that the software project i was on is finished. there's an unholy amount of garbage and spaghetti that i have to wade through and eventually fix. this throws a major curve ball at my mental model. but i'm glad it's getting fixed now rather than later. so thank you. 🙇‍♂️ ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 4, 2024, 5:21pm UTC](https://forum.inductiveautomation.com/t/custom-session-props-in-master-do-not-propagate-to-slave/83792/8 "2024-01-04T17:21:07Z")
Project events (gateway, client, session) are going to be separated resources in 8.3, at least. Session properties will almost certainly continue to be all-or-nothing, though we do need to come up with better UI to present to you. Right now, you (as far as I know) have to manually _delete_ the resource from your "child" project(s), and then the next time you load the project in the Designer you'll get the implicit inherit copy from the parent project. Then, making _any_ modifications in the child project's copy will implicitly override it and give you a local copy at that moment in time. ---
**Author:** ![ian.sebryk](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ian.sebryk/32/49319_2.png) [@ian.sebryk](https://forum.inductiveautomation.com/u/ian.sebryk)\ **Post date:** [January 4, 2024, 6:39pm UTC](https://forum.inductiveautomation.com/t/custom-session-props-in-master-do-not-propagate-to-slave/83792/9 "2024-01-04T18:39:50Z")
that's perfectly fine. i WANT to have the ability to override for specific cases, but in general, i want the Master's custom session props to show up in the Slave project, at least _initially_, upon creation. i guess the better workflow would be to FIRST make the Master, THEN set it as such in the Gateway, THEN create the Slave... at least that's how it presents itself in my head after your post. but when you're running as cleanup crew, you rarely gets the clean slate, eh? 😛 this was useful. thanks Paul. 👍