Assign View To Multiple Data Sources

[Grant_Stead]

Often I find myself needing to create duplicates of the same views to apply to different slices of the same data. (Slices used to control inline, etc…) Then when I make one change, I have to go find all the different forms, etc. and try and make sure I’m matching them for a consistent app experience.

Honestly, this feature request simply treats numerous symptoms of other issues.

[Grant_Stead]

And no, I’m not voting for my own feature request. It is not currently more valuable than many other requests. @everyonethatwishestheyhadmorevotes

[MultiTech]

Grant_Stead:

Often I find myself needing to create duplicates of the same views to apply to different slices of the same data.

Amen brother! You got my vo…

[Grant_Stead]

Hahaha

[Rafael_ANEIC-PY]

That would be really smooth, voted!

By the way, do you get back your votes when the requested features are implemented? i remember this thread from some time ago

Number/Decimal column step size should not determine validity Questions

When you have a number or decimal column where you specify an increase/decrease step size, it seems that this causes some internal validity check that any manually entered inputs must be a multiple of the step size. This seems extraneous given that we can already specify our own valid_if expression to cover this if we want, and I see no reason why this should always be forced. Consider a situation where you need to allow decimal inputs to a column, however most of the time the inputs are just i…

I think it has been implemented already, but i still haven’t got my vote back

[Steve]

Can others confirm this has been fixed?

[Marc_Dillon]

EDIT: See below. appears to be fixed.

I don’t think that was ever fixed.

Confirmed: not-fixed:

---

[Rafael_ANEIC-PY]

My bad guys, i thought it was working, this is what i tested:

[Marc_Dillon]

Hmm, interesting. Did you click out of the field after entering the number?

[Austin]

Yours is invalid due to the decimal digits being 1 and 1.45 having 2 decimals.

[Marc_Dillon]

Austin_Lambeth:

Yours is invalid due to the decimal digits being 1 and 1.45 having 2 decimals.

You’re right!
I guess this is fixed? Wooo!

[Austin]

Finally. Although I am not above thinking that it could just be broken in a different way we haven’t found yet.

[Marc_Dillon]

Austin_Lambeth:

it could just be broken in a different way we haven’t found yet.

…so true

[Marc_Dillon]

Did we hijack this thread enough yet? I could tell a story…

[Austin]

I casted one of my last vote for it so that makes up for it

[Grant_Stead]

Hijack away!
(I honestly just post feature requests to start a conversation!)

Kinda excited you got your column definition fixed!