unsaved or cloned rows lose their unsaved status when adopted

  • Hi Pat, thanks for bringing this issue to our attention.

    What version of Skuid are you running?

  • Did you notice the behavior in api v1 and/or v2?

Use Case: You have unsaved rows in model A that you clone/adopt into model B. Are you saying that the rows don’t stay unsaved in model A? or that aren’t marked as new/changed rows in model B?

If you could throw together a simple repro page using standard objects, that will help us determine if the behavior is expected or not. Thanks!