Hey Daniel,

Thanks for the quick response. Makes sense, it does work when using the non-html workflow as well, so hopefully this wouldn't be a big change to Umbraco Forms if they could implement it.

Thanks,

-M

For anyone that runs into this issue, there is a workaround for this problem. It requires a custom workflow unfortunately, but it fairly straightforward and can be seen below (this implementation is for umbraco 8).

public class CustomSendRazorEmail : SendRazorEmail {

    public CustomSendRazorEmail (IHttpContextAccessor httpContextAccessor, IFieldTypeStorage fieldTypeStorage, IFormStorage formStorage, IUmbracoContextAccessor umbracoContextAccessor, IPageService pageService, IWorkflowEmailService workflowEmailService) : base(httpContextAccessor, fieldTypeStorage, formStorage, umbracoContextAccessor, pageService, workflowEmailService) {
        Id = new Guid("{unique id}");
        Name = "Custom Send Razor Email";
        Icon = "icon-message";
        Group = "Services";
    }

    public override WorkflowExecutionStatus Execute(Record record, RecordEventArgs e) {
        var uploadFieldId = new Guid("{id of custom upload field}");
        var uploadFields = record.RecordFields.Where(x => x.Value.Field.FieldTypeId == uploadFieldId);
        //this is a hack to get umbraco forms to attach files from a custom upload field
        foreach (var uploadField in uploadFields) {
            uploadField.Value.Field.FieldTypeId = new Guid(Constants.FieldTypes.Upload);
        }
        var result = base.Execute(record, e);
        foreach (var uploadField in uploadFields) {
            uploadField.Value.Field.FieldTypeId = uploadFieldId;
        }
        return result;
    }
}

Umbraco forms only attaches files from the built in upload field, so the hack involves assigning that id to the custom upload fields. This will get the base class to attach those files when it's executed. It then reverts those id changes to avoid causing problems in future workflows. This is definitely a hack, but it will work until we get a proper fix for this problem (issue filed in bug tracker here).

is working on a reply...