I have experienced this. You must make sure that required fields are mapped (e.g. Title field) and that the mappings are of the correct data type e.g. Numeric, DateTime if you are mapping them on to a field that accepts an integer or date.
You can try a basic experiment with creating a form that creates a Basic Page or Article to check all works - note the above. It definitely works as I have a custom content type with a dedicate bundle that is successfully created.
OK thanks, I had not appreciated the VBO field was effectively another form.
Oh how I wish I had found this a few days ago... I spent hours trying to track it down and I thought it was to do with a Webform Validation Handler I had written. https://civicrm.stackexchange.com/questions/48120/custom-webform-handler....
It makes no difference whether the filter uses Autocomplete - we pass in Contact IDs and its static at the beggining, it is purely the #group, even 'None'.
Thanks Jacob - no problem, I'll work around. Thanks for all your work on a truly awesome module!
I spent about an hour on this today trying to get it to work before going through the debugger and seeing that it was using the drupal database. Might be worth mentioning that in the readme somewhere that if you have a separate database to ensure that the $databases is set up! Thanks anyway for a great module :-)
Updating the original question as this relates to Views that have a base table of CiviCRM Cases
Hi Mark
I have just created the most simple of Views that just displays the same list of contacts. This View works fine, which must mean that it is the relationship to CiviCases that may be the issue. The View that has the issue has a base table of CiviCRM cases displays a list of case clients (amongst other details). Not sure if this helps, but it clearly is not just a plain Contact Entiry issue, as you rightly say, this works OK in isolation
Hi Mark
Many thanks. Here is a gist of the View's config. I duplicated the original and made it as simple as possible, taking out all the other stuff that is not applicable to the issue. There are just the two contact fields that do not display.
It does require a bit of setup as we have a CiviCRM installation with a fair few custom fields. I'll try to create a 'minimum' example of where it will fail. One of the issues is that the you cannot tell from the logs exactly what the issue is. Of the various things that happen on the import, which one exactly triggers the problem, my guess is access to a custom field. In the meantime, I've solved the pressing issue from the other direction, i.e. giving overly permissive permissions to the anonymous user for the duration of the import. The Drupal permission required to be set is:
CiviCRM: all CiviCRM permissions and ACLs
Administer and use CiviCRM bypassing any other permission or ACL checks and enabling the creation of displays and forms that allow others to bypass checks.