Revit 2026 – Type Properties / Instance Parameters not updating correctly

[red72TKB]

Hi all,

Since updating to Revit 2026, I’ve run into an issue where parameter edits don’t “stick” if I change two values in the same dialog.

Example 1 (Type Properties):

• Open Type Properties of a family.

• Edit Parameter A → saves correctly.

• Edit Parameter B → reverts back to old value after hitting OK or Apply.

Example 2 (Structural Beam Offsets):

• Select a beam.

• Edit the Start Level Offset → value updates correctly.

• Then edit the End Level Offset → the new value does not stick. It reverts, and I have to re-enter it for it to apply.

Notes:

• This only occurs in Revit 2026.

• Tested on both type and instance parameters.

• Behaviour is normal in 2025 and earlier versions.

Is this happening to anyone else in Revit 2026? Is this a known bug, or is there a workaround apart from re-entering or clicking Apply after each parameter change?

This is annoying me enough that I'm about to install Archicad because they also do Vector Shadows.

[blank...]

---

@red72TKB wrote:

Is this happening to anyone else in Revit 2026?

---

No, can't confirm, works OK.

---

This is annoying me enough that I'm about to install Archicad because they also do Vector Shadows.

---

If you do, could you come back after 3 months of using Archicad and share your experience.

[red72TKB]

Thanks for your help.

[TripleM-Dev.net]

Maybe something with the family or constraints, or focus of mouse shifts, read some posts about 3D space mouse (drivers) causing wrong input place or not sending a mouse click correctly.

Try it with one of the stock doors or a wall changing type / instance parameters.

[red72TKB]

I'm finding it hard to believe that nobody else is having this issue on 2026. It is happening to two others at my workplace and also on my home computer. If one of my clients hadn't switch over to 2026, I would revert back to 2025.

[PRCHABOT]

I am also experiencing this problem.  I just updated a Detail View's "View Name" parameter and "Title on Sheet" parameter, selected a different field within the properties window while keeping my cursor within the window, verified the values looked correct, then moved my mouse clear of the window and watch the "Title on Sheet" parameter revert to blank.

I then tried to recreate the problem four more times with the same parameters and both updated fields held their changes.  I also tested other elements and those also retained their modified parameter values.

I do recall previously having this problem with framing elevations enough for me to change my workflow to updating one end elevation, applying / moving mouse away, then updating the second value so that I wouldn't lose any edits to a second parameter that wouldn't save.

I check for updates daily and apply them as soon as they are available, so I'm pretty sure I have the latest version of Revit (26.3.0.37, 20250908_1515(x64)).  As mentioned, this isn't the first time I've had the problem, but I haven't documented previous occurrences and can't say if I updated Revit before or after the previous occurrences.

[red72TKB]

Yes, this is the problem. I think it can be mitigated by hitting apply after changing only a single parameter, but this is a much slower workflow than previous Revit versions. I might submit this as a bug.

[ferdi]

I can also confirm to have this issue.

Extremely annoying, using custom or built-in functions/families happens all the time.

Also have installed all the updates available in the hopes of a fix but nope...

Yet to find the reason or solution for this.

[nickdeal]

Can confirm as well.  Tried entering data in multiple text fields only to find is accepted just the first.

[gorik.vansteenbergheTLLJE]

I've found out what causes the problem for me.

What I did was using the arrow keys in the properties tab and changing values like I did in Revit 2025. This doesn't work in Revit 2026, you have to click on the value with your mouse. Then you can change multiple values at once.

This is pretty annoying if you are used to change values with the arrow keys. I hope they change this back, otherwise it's getting used to making more mouseclicks.

[PRCHABOT]

This is a big help!  I did more testing and confirmed than any field that was entered using arrow keys did not save. 

I also tested <tab> and found that fields that were tabbed into retain their values.  It's just the arrow keys that seem to be the problem.

Thanks for the insight!

[red72TKB]

Yeah, I found when using tab it wouldn't have the same issue but the problem with tab is that when you first place a beam it has this greyed out parameter named Orientation: Normal. I would edit the Start Level Offset and then tab to the one below and it would jump to Cross-Section Rotation. I'd then have to arrow back up which results in the same problem. 

So anyway, the tab workflow works after the beams offsets have been changed already. As gorik.ventsteenbergheTLLJE said above, the issue seems to be the arrow keys. Hopefully they can fix this soon, having to click each time is much slower.

[PRCHABOT]

I do hate how that happens with tab, but in case you (or anyone else) don't know, instead of arrowing back up, you can use "shift + tab" to tab "backwards" up list.  That will be my go to work around.

[red72TKB]

Yeah, tried that and I think it's still slower than using the mouse unfortunately.