Not properly interacting with imported data

I cant exactly say if my issue is caused by editable fields or not however the behavior I am noticing is that it only occurs during manipulation via an editable field. With that disclaimer in mind let me try best to summarize my issue.

I use an editablefields dropdown list within a view that is used to change the the paystatus field within a custom 'Invoice Release' node that I have created from "open" to "closed". Editibale fields does a wonderful job allowing an administrator to manipulate this field within their view so that its status is changed for our users view on the production site. Within my development site after I import specific tables to sync some production content (ie node, node_access, etc) my view still loads properly (and reports properly in the view's module) however when using the editable fields dropdown to change the status on 'production content' the status is changed in the node, however dissapears from the users view and is only seen within User 1's view.

I have noticed that if i opt not to first manipulate the status of production content with the editable field and edit the node directly then the status is changed and it appears properly within the users view, as well after that point I may use the editable field and it works as I would expect it to changing the status and appearing in the view for production content for all proper users. On the flip side there is no problem with newly created content in development and editable fields interaction, only production data act's this way.

I have spent a few hours looking at the tables and comparing table data here and there, are there specific table's that I should be considering to import into newer versions that could be the cause of this? As of current I import the following tables into my development environment;
[ content_type_invoice_release, files, invoice_customers, invoice_items, invoice_templates, node, node_access, node_comment_statistics, node_revisions, users, users_roles]

In the short term I can work around this though I fear as the content grows this will no longer be feasible. Any suggestions that you may have would be greatly appreciated and hopefully are just the results of a table relating to editablefields that I have not imported properly.

Thank you for your expertise,

M