December 11, 2008 at 11:33 am
Sorry to post something that may have been hashed over already, but I am almost out of hair.
The problem I have is this exactly http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3953458&SiteID=1
But I don't have the error in the logs they describe 'GetItemTypeAction(/).' and can't figure out what user permissions I need to give to the catalog?
This was working fine a week ago, I did redeploy some things but have never altered any rights.
Any help would be VERY VERY VERY Appreciated.
Thanks in advance.
December 11, 2008 at 3:56 pm
cross (12/11/2008)
Sorry to post something that may have been hashed over already, but I am almost out of hair.The problem I have is this exactly http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3953458&SiteID=1
But I don't have the error in the logs they describe 'GetItemTypeAction(/).' and can't figure out what user permissions I need to give to the catalog?
This was working fine a week ago, I did redeploy some things but have never altered any rights.
Any help would be VERY VERY VERY Appreciated.
Thanks in advance.
Can't say I have experienced this problem but might have a few things for you to look at. The filters/prompts values get generated based on the data supplied back from your model generated queries, so it will contain only values that are valid. Take a look at profiler and see what query the dropdown is trying to get for the filter. I would expect something like "select distinct A From Table..."
See what that is and make sure it is returning correctly. It might be that there is a mismatch between the model, the queries and tables. Let me know if you find anything out or have additional info and I'll see if I can help more.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy