Saving nested items with class hierarchies

[atjohns]

This is a similar issue to a very old discussion posted here on class hierarchies in Dynamo, but this one is explicitly about saving items. I am trying to use DynamoDB to save a model that mimics the following structure

    public class A
    {
        public string Name { get; set; }

        public int MyPropA { get; set; } = 1;
    }

    public class B : A
    {
        public int MyPropB { get; set; } = 2;
    }

    [DynamoDBTable("Test")]
    public class ModelA
    {
        [DynamoDBHashKey]
        public Guid id { get; set; }

        public List<A> MyClasses { get; set; }
    }

If we instantiate a new instance of this model like so...

            var a1 = new A { Name = "A1" };
            var b1 = new B { Name = "B1" };

            Guid id = Guid.NewGuid();

            var model = new ModelA
            {
                id = id,
                MyClasses = new List<A> { a1, b1 }
            };

We end up with a list that contains both Class B & Class A types. However when this model is saved to Dynamo it only saves the Class A properties. Here's a screenshot showing what the object looks like when the Save call is made vs what it looks like within Dynamo

[dscpinheiro]

Since that issue is old (and like you mentioned, not exactly the same problem), could you open a new one? https://github.com/aws/aws-sdk-net/issues/new/choose

We'll look into it.

[ashishdhingra]

Closing this discussion in favor of #2985.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.