Assuming you are using 3rd party mibs that you had to import I believe I solved this last night. I have a case open with tech and am waiting to hear their response but my custom flexview is now working in OneView.
I knew that refreshing the Flexview in OneView was not generating traps by doing a tcpdump on the NetSight server which is OneView operates from. It is important to note that this behavior is different than that of Console which runs from and uses the mib file stored on your pc.
Apparently the problem is the OneView is not looking in the MyMib folder and is therefore unaware that it has access to the mibs the custom flexview is referencing. To make it work I placed the mib file in the base mib folder and now all is well. I am attaching screen shots of both file paths for clarity.
This is where I understood mibs should be imported too so that they don't get overwritten by future updates. This folder also seems to sync with the folder on your pc that Console looks in.
This is where I had to put the mib to make my Flexview work in OneView