The most obvious thing to check is whether the next in quotes is the exactly correct name of a field and that the field name was not changed after this step was created.
What's your context? If "Order_ID" is not a field defined in the table on which your current layout is based, you need to include the "fully qualified" field reference--which will be in this format: "TableName::FieldName".
You might want to consider using getfieldname in the second parameter.
If that's not it:
What's the actual name of your file?
If you put the name of your file in quotes, does the function work?
Does your file have more than one period in the file name?
@PhilModJunk - Thank you.
The first couple of suggestions are typical mistakes when it comes to this function so they were the first ones I checked. But your last suggestion ("does it have more than one period") was the culprit. I recently started renaming my code to denote versions... ex. RC2.1.fmp12 which does contain more than one period. When a replaced the 2.1 with 2-1 it started working again. Thanks you.
This is a recently identified bug that can affect a number of design functions.
For More Information see: ValueListItems() fails if there is a period in the filename
This is one of many acknowledged bugs that can be found in the Known Bug List thread here in the Report an Issue section of the forum.
It can also be downloaded as a database file from: https://www.dropbox.com/s/jt09b82i0xijbu3/FMP%20Bugs.zip