Hello Ronald,

Thank you for the response. I've tried you're suggestion but still did not work. Here's how I added the scope provider:

    private readonly IContentService _contentService;
    private readonly IDataTypeService _dataTypeService;
    private readonly IUmbracoContextFactory _umbracoContextFactory;
    private readonly ILogger _logger;
    private readonly IScopeProvider _scopeProvider;

    public SampleComponent(IContentService contentService, 
        IDataTypeService dataTypeService, 
        IUmbracoContextFactory umbracoContextFactory, 
        ILogger logger,
        IScopeProvider scopeProvider)
    {
        _contentService = contentService;
        _dataTypeService = dataTypeService;
        _umbracoContextFactory = umbracoContextFactory;
        _logger = logger;
        _scopeProvider = scopeProvider;
    }

Here's how I used it:

        using (IScope scope = _scopeProvider.CreateScope())
        {
            //populate dropdown - NOT WORKING
            var newValueList = new List<ValueListConfiguration.ValueListItem>();
            newValueList.Add(new ValueListConfiguration.ValueListItem
            {
                Id = 1,
                Value = "TEST VAL ONE111"
            });
            newValueList.Add(new ValueListConfiguration.ValueListItem
            {
                Id = 2,
                Value = "TEST VAL TWO222"
            });

            var dropDownTest = _dataTypeService.GetDataType(1515); //target dropdown datatype
            ((ValueListConfiguration)dropDownTest.Configuration).Items.AddRange(newValueList);
            _dataTypeService.Save(dropDownTest);

            scope.Complete();
            _logger.Info<ContentNodes>($"Dropdown Entries Added");
        }

Breakpoint hits it and logs displays the logger message so I know this is being hit. However, the two values are still not being added to my target dropdown data type.

Thank you again.

I've just tested this out on a clean Umbraco 8.18 site and looks like the data type service already creates its own scope, so that's not even required.

The following code correctly replaces all existing items of the default dropdown data type:

using System.Collections.Generic;
using Umbraco.Core;
using Umbraco.Core.Composing;
using Umbraco.Core.Models;
using Umbraco.Core.PropertyEditors;
using Umbraco.Core.Services;

public class ApplicationComposer : ComponentComposer<ApplicationComponent>, IUserComposer
{ }

public class ApplicationComponent : IComponent
{
    private readonly IDataTypeService _dataTypeService;

    public ApplicationComponent(IDataTypeService dataTypeService) => _dataTypeService = dataTypeService;

    public void Initialize()
    {
        var dataType = _dataTypeService.GetDataType(Constants.DataTypes.DropDownSingle);

        var items = new List<ValueListConfiguration.ValueListItem>()
            {
                new ValueListConfiguration.ValueListItem
                {
                    Id = 1,
                    Value = "TEST VAL ONE111"
                },
                new ValueListConfiguration.ValueListItem
                {
                    Id = 2,
                    Value = "TEST VAL TWO222"
                }
            };

        dataType.ConfigurationAs<ValueListConfiguration>().Items = items;
        _dataTypeService.Save(dataType);
    }

    public void Terminate()
    { }
}

It might be timing (hence the IUserComposer, so it runs after all core ones), custom logic cancelling save or some other issue, so make sure to check your logs and audit trail.

Hi Francis,

I've tested the above sample code on a clean 8.14.1 install and it updated the data type configuration without any issues, so it must be something else in your code (e.g. not completing a scope, causing all changes to rollback).

You can indeed check the logs in Settings > Logs (or on-disk in App_Data\Logs). I checked the audit log and it data type saves aren't audited (they don't cause a row being added to umbracoAudit).

My advise would be to start debugging code and try to isolate what's causing this to not work, either by stripping out/disabling code from your existing solution or adding bits to a clean install and seeing when it starts/stops working...

Thanks Ronald. I'll be sure to take a look and let you know.