Hi Amber,
A few tips....
If you have not created an OVS before, I would start with a standard object first. To get an idea how it works with an existing BO. Lets us Service Category BO as an example... Here is a copy of the solution. Load into your solution so you can see it...
1. Bind it to the Service Category BO -> Query By Hierarchy. Notice that you create data model elements under the search parameters structure for each filter field. I noticed you mapped multiple parameters to the same query data model element/value
quick tip, click on ... button
right click on the searchparameters structure and choose add data field. It will create a new data field and bind it and name it the same as the filter parameter in one shot.
2. define some inports you want to default the filter panel.
3. bind the object ID to the ID in the data model (you can always add your own ID field but this will at least keep it easy to show the ID field everywhere in the OVS) without further adjustments. do the same for object name to the name ...
4. do nothing for the outport (since you used the standard object ID and object name)
5. object name and object ID are standard fields in the list. I renamed the title of the columns of Service Category/Category ID respectively.
Then use this OVS on any field for a test.... this general how to will work on all standard objects. Once you get this working you can replace the query with a SADL query to make it performant since SADL queries are the best practice way to configure an OVS
For a custom object, I have always bound the Object ID field as the "alternate key" field of the BO. Above "ID" is the alternate key for service category BO...