# Refresh needed to inherit changes? **URL:** \ **Category:** Ignition\ **Created:** [April 24, 2023, 2:18pm UTC](https://forum.inductiveautomation.com/t/refresh-needed-to-inherit-changes/72822 "2023-04-24T14:18:39Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![rpulsifer](https://avatars.discourse-cdn.com/v4/letter/r/e9a140/32.png) [@rpulsifer](https://forum.inductiveautomation.com/u/rpulsifer)\ **Post date:** [April 24, 2023, 2:18pm UTC](https://forum.inductiveautomation.com/t/refresh-needed-to-inherit-changes/72822/1 "2023-04-24T14:18:39Z")
In the section under "Inheritance", it says: > When project resources are changed in the original project, these changes will get passed down to the inherited projects. But, I've added a custom Session property to my global project and it doesn't show up in existing projects. They do show up when you create a new project, but changes do not turn up once the project has been created. Is there a way to force a refresh to push these changes down from the global project? Or aren't custom props considered "resources"? ---
**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:** [April 24, 2023, 4:45pm UTC](https://forum.inductiveautomation.com/t/refresh-needed-to-inherit-changes/72822/2 "2023-04-24T16:45:04Z")
The complication is that session props, among a few other types of resource, are a _single_ resource. Project inheritance works on the individual resource level; so you either have the inherited session properties, or your own. It _cannot_ work on the level of individual session properties, because the project resource system is not aware of _how_ to manage inheritance for individual resource types added by individual modules. ---
**Author:** ![rpulsifer](https://avatars.discourse-cdn.com/v4/letter/r/e9a140/32.png) [@rpulsifer](https://forum.inductiveautomation.com/u/rpulsifer)\ **Post date:** [April 24, 2023, 5:14pm UTC](https://forum.inductiveautomation.com/t/refresh-needed-to-inherit-changes/72822/3 "2023-04-24T17:14:32Z")
Thanks for the clarification. Makes sense why they are there on a new project but changes or additions don't show up automatically..... (sigh) ---
**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:** [April 24, 2023, 5:26pm UTC](https://forum.inductiveautomation.com/t/refresh-needed-to-inherit-changes/72822/4 "2023-04-24T17:26:32Z")
In the short-to-medium term, we're planning to make it more clear what the inheritance state of these resources is and allow you to choose to override changes. There's an _outside_ chance, when that happens, that _in the Designer_, we'd be able to show some kind of conflict merge UI. No promises, though. ---
**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:** [April 24, 2023, 5:28pm UTC](https://forum.inductiveautomation.com/t/refresh-needed-to-inherit-changes/72822/5 "2023-04-24T17:28:21Z")
> [@paul-griffith](#): > > some kind of conflict merge UI Instead, can you simply break the resources up into individual resources? Maybe a convert on first save rule like XML for Vision windows. ---
**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:** [April 24, 2023, 5:29pm UTC](https://forum.inductiveautomation.com/t/refresh-needed-to-inherit-changes/72822/6 "2023-04-24T17:29:31Z")
How would that work for session props? A bunch of tiny resources per key? It _is_ in the pipeline for 8.3 for other singletons like client/gateway/session event scripts, though. That's obvious, low-hanging fruit stuff. ---
**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:** [April 24, 2023, 5:32pm UTC](https://forum.inductiveautomation.com/t/refresh-needed-to-inherit-changes/72822/7 "2023-04-24T17:32:05Z")
> [@paul-griffith](#): > > A bunch of tiny resources per key? One json definition file "X.json" for `session.custom.X` and all of its nested elements. In other words, draw a line in the sand at a reasonable/intuitive level of granularity. There's nothing fundamentally wrong with _tiny_ resources. They just need to have deterministic content to be git-friendly. ~~Psst! Project events, too! One "X.json" for the event configuration, and "X.py" for the script. In folders by event type.~~ _Already noted._