Expected Behavior

Custom data types should be able to update security OHLC properties if they contain user defined OHLC fields that follow a name convention (e.g: "Open", "High", etc.)

Actual Behavior

Custom data types update all OHLC security properties with a single fixed value from their Value attribute

Potential Solution

N/A

Checklist

• I have completely filled out this template
• I have confirmed that this issue exists on the current master branch
• I have confirmed that this is not a duplicate issue by searching issues