Some custom fields not available in Drupal Views after upgrading to 4.2

[mostou]

After upgrading to 4.2 from 4.1.3 some custom fields are not available in Drupal Views.

I have tried:
- cleared all caches (in Civicrm, Drupal and Drupal views)
- tried to create a new custom field group (not working)
- checking the settings.php file (making sure that the relevant custom field tables are listed)
- resaving all custom field groups
- checking and optimizing custom field tables in database (in case a table needs to be repaired).

Nothing solved the issue. See also:
http://forum.civicrm.org/index.php/topic,25868.0.html

Russneversleeps wrote:
"Looking at my custom data sets, and running a few tests, it appears that Views is only pulling 1 custom data set for each record type."

I have now reverted the upgrade. Have anyone else experienced this issue?

[Coleman Watts]

Please do not cross-post the same issue to multiple boards, thanks.

[mostou]

I didn't cross post - I have posted an upgrade issue here and mentioned that another person has registrered the same issue in another board. Since this issue is related both to upgrading to 4.2 and to using a Drupal module it is not wrong to post the issue in this board as well. Now the issue is handled in the original post by "Russneversleeps", so in my oppion this topic can be locked with a reference to the other topic.

[kreynen]

@mostou, I think you handled this as well as possible given the limitations of using a forum as an issue tracking tool. 

@Coleman Watts, If an issue involves Drupal and Upgrading to 4.2, why wouldn't there be references in both topics? What is the downside of cross posting?

[Coleman Watts]

If an issue is posted in multiple places then it becomes difficult to see what's going on - people will post to both threads and there will be no coherent conversation.
Lots of topics could be justified as belonging to multiple boards, but don't you think this forum is crazy enough as-is without everybody doing that?

[mostou]

@kreynen, I think you are right, a forum is not the best issue tracking tool - especially with so many sub-boards

@Coleman, it was not my intention to create more confusion - on the contrary that is why I made a double reference in both topics, to avoid parallel discussions of the issue.

But however with so many sub-boards I was not certain it was rated with the right priority or even read, when posted in the " Using Drupal modules"-board. Since I considered the issue more a critical upgrade issue I posted it as well in the upgrade board. Sorry if it has created confusion, but I would do it again, if I think a post is rated too low due to the board it is posted in (for instance if an upgrade issue is posted in a less active board, like this issue). And remember I didn't create two topics in two different boards - I answered one topic and created a new topic in the board I found more appropriate for this issue and posted references in both topics.

Again someone may lock this issue as a duplicate for my sake since it is handled in the original post.

I don't see a problem in cross posting as long as references are made and one of them are getting locked when the issue is starting getting handled.