Okay- I have a large DB (21 GB) - I have docments showing in a view where the column w/ the formulaDecktype
shows Gypsum
but when the document is opened, the decktype field does not show Gypsum and the field in the Properties dialog does not show gypsum-
I have run fix up, the problem persists
which is right, the View, the document? None of the above?
Ideas on solving the issue?
while not helpful perhaps- when you search the view, the documents come (using the “more” search feature and doing seach by field) - even though when you open them, the data does not display.
Subject: View V Document data difference
I would assume, that the document properties are as close to the item content, as you can get through the UI. If so, the problem should be with the view index, so fixup is not likely to fix the problem.
Can you try to rebuild the index manually?
Is the value Gypsum anywhere in any item of these documents? Are you sure, that there is no column in that view with a programmatic name of Decktype (although I’m not sure off hands, what should win)?
And out of curiosity: Is this database that large because of hundreds of thousands of documents (which might make problems with view indexes more likely) or because of large attachments?
Subject: RE: View V Document data difference
Harkpabst, The answer is a little bit of both- there are 500,000 documents in the db- (60,000 in this particular view) - but we do have attachments and we (in the IT dept) have found that people are "pdf"ing the documents, e-mailing the pdf to the client, and then attaching the pdf (of the document) in the document. Certainly that was not the intent- but there are also photographs of the jobs (this data base contains warranty information) - We are currently revisiting how, what and why attachments are put in.
I have to vpn in this morning and I will check the column issue- can't imagine that is it as the persons who created this db (I have worked for the company for 4 months) weren't really adept at that.
Thanks for your ideas.
Tom
Subject: a few clarifications please
what is teh exact view selection formula?
is there a form formula on the view?
what is the type and formula for the DeckType field on the relevant form or forms?
what is the information from DeckType item on a document that shows this problem i.e. Item type and values and flags.
Subject: RE: a few clarifications please
View selection formula isSelect Form = “TechData”
No, there is not Form formula
Decktype is a text field of type Dialog List
What shows the problem this- it started w/ an “Advanced search” - Form = “TechData” & Decktype = “Gypsum”= the search brought up a number of documents, some of them correctly and some of them where the value of decktype was empty.
So, I actually created a new view- bringing in only Decktype & JobNumber fields. - At first I categorized it, then took that away- most are coming in correctly- though a significant number being brought in have “Gypsom” in the view column (Decktype is the formula) , but when you open it, that field is empty- and when you look at doc properties, the Decktype field is empty.
I did run compact -c on it today, telling it to blow away all indices and rebuild them. That did not solve the issue.
Subject: Problem discovered
I know this has fallen off the forum radar screen- but perhaps it will help- I figured out the problem this morning- the field in question (DeckType) is a Combobox field w/ “Allow Values Not in List” UNCHECKED - there is a @Dblookup formula that provides the list. So, the view formula, which simply is DeckType displays the value- but when you open the document, since it is not in the list, it won’t display it- NOT EVEN IN THE DOCUMENT PROPERTIES box!!! Even more bizzare (I think) is it is simply casing- in other words- GYPSUM - plankis in the look up but
GYPSUM - PLANK
is not- and thus Domino sees it as unacceptable.
To the naysayers (and I would have been one of you!), I entered the second entry in to the list, exited the database, came back in, opened up one of the documents in question and it works and is in the properties dialong box! I have taught Lotus Notes programming for 20 years- have always said “Always assume Lotus notes is ALWAYS case sensitive, even when you think it isn’t, because it will bite you!” This might be exhibit A- thanks for those who had suggestions.
Tom
Subject: RE: Problem discovered
I think the main lesson to learn is as simple as important:
Always check your item values from the view level, if you really want to know what’s in there. It slipped my attention, that you had not explicitly stated you had done this in your original posting. And that lead me on the wrong track.
Lesson No 2: The view index is right, even in 21 Gig databases. 