Not sure if this is a bug or feature. I defined a feeds importer. I wanted to update a bunch of nodes across different bundles - they all shared the same field. But feeds only allows the selection of one bundle. That probably makes sense for displaying the mapping options. I had assumed that the import would update the nodes only for that bundle and skip the nodes in the csv for the other bundles. (I set nid as the unique field). Turns out, however, that they all got updated. So now I don't have to duplicate the importer for each content type. In my case that worked well. I didn't want it to create new nodes or delete non-existing. But if those were enabled, I'm curious what the result would be.
Maybe a description on the bundle selection that nodes not in the bundle may still get updated if they are in the source and the fields match.
Not sure if this is a bug or feature. I defined a feeds importer. I wanted to update a bunch of nodes across different bundles - they all shared the same field. But feeds only allows the selection of one bundle. That probably makes sense for displaying the mapping options. I had assumed that the import would update the nodes only for that bundle and skip the nodes in the csv for the other bundles. (I set nid as the unique field). Turns out, however, that they all got updated. So now I don't have to duplicate the importer for each content type. In my case that worked well. I didn't want it to create new nodes or delete non-existing. But if those were enabled, I'm curious what the result would be.
Maybe a description on the bundle selection that nodes not in the bundle may still get updated if they are in the source and the fields match.