Btukfyl

I am busy writing a bot that interacts with both anonymous and authenticated users. It stores user data in a custom object and persists that object to the UserState Store.

When the bot starts and the user joins the conversation it creates the custom object and the IStatePropertyAccessor for the custom object. the bot then determines if this is a authenticated or anonymous user. If its authenticated, it loads the required information from the backend system and we are able to use this data in all dialogs without issue.

If it is an anonymous user we direct them to a basic dialog that gets their name, phone number, and email. The last step in this dialog is to pull the above custom object and update it with the information collected so we can attach it when saving requests to the backend system.

The problem is that the updated information is saved to the store (I am able to view the raw data in the cosmosDB), but when getting the custom object from the store in other dialogs it always returns an empty object. If I trigger the onboarding dialog again, it pulls the correclty populated custom object fine.

Why is that this one dialog can see the data it saved to the store but other dialogs see it as an empty object?

Below is my code for the final step in the onboarding WaterfallStep dialog:

public async Task<DialogTurnResult> ProcessOnBoardingAsync(WaterfallStepContext stepContext, CancellationToken cancellationToken)

    {

        _form = await _accessor.GetAsync(stepContext.Context);

        _form.Firstname = (string)stepContext.Result;



        UserProfile profile = await _userAccessor.GetAsync(stepContext.Context);



        profile.FullName = String.Format("{0} {1}", _form.Firstname, _form.Lastname);



        await _userAccessor.SetAsync(stepContext.Context, profile);



        MainResponses view = new MainResponses();

        await view.ReplyWith(stepContext.Context, MainResponses.Menu);



        return await stepContext.EndDialogAsync();

    }

After this step, the raw data is correct, the Fullname is set correctly. It can be viewed in the raw data stored in CosmosDB.

the next dialog's constructor is as follows and the IStatePropertyAccessor<UserProfile> userAccessor that is passed in to this constructor is the same one passed into the Onboarding Dialog constructor:

public LeadDialog(BotServices botServices, IStatePropertyAccessor<LeadForm> accessor, IStatePropertyAccessor<UserProfile> userAccessor)

        : base(botServices, nameof(LeadDialog))

    {

        _accessor = accessor;

        _userAccessor = userAccessor;



        InitialDialogId = nameof(LeadDialog);



        var lead = new WaterfallStep

        {

            LeadPromptForTitleAsync,

            LeadPromptForDescriptionAcync,

            LeadProcessFormAsync

        };



        AddDialog(new WaterfallDialog(InitialDialogId, lead));

        AddDialog(new TextPrompt("LeadTopic"));

        AddDialog(new TextPrompt("LeadDescription"));

    }

and the code that is trying to use the accessor is:

public async Task<DialogTurnResult> LeadProcessFormAsync(WaterfallStepContext stepContext, CancellationToken cancellationToken)

    {

        _form = await _accessor.GetAsync(stepContext.Context);

        _form.Description = (string)stepContext.Result;



        await _responder.ReplyWith(stepContext.Context, LeadResponses.LeadFinish);

        await _responder.ReplyWith(stepContext.Context, LeadResponses.LeadSummary, new { _form.Topic, _form.Description });



        UserProfile profile = await _userAccessor.GetAsync(stepContext.Context);





        var LeadDetail = new CRMLead

        {

            ks_chatid = profile.Chatid,

            parentcontactid =profile.ContactId,

            topic = _form.Topic,

            description = _form.Description

        };

    }

In this last bit of code, the returned UserProfile is an empty object with default values, but would have expected to at minimum pulled the Fullname that is correctly stored in the CosmosDB.

It turns out that a fellow developer had made the set properties on the User Profile class as internal so the accessor could not set the properties when reading the store.