I receive a handful of messages from individuals via the built-in "send a message" تابع مایکروسافت فراهم می کند با فضای زندگی می کنند (که همچنین میزبان وبلاگ من) هر ماه.
حدود یک سوم از زمان, those users have secured their live spaces account such that I cannot reply. This is some kind of anti-spam feature I assume.
</پایان>
تکمیلی: An anonymous poster left a great comment about internal names. Be sure to read it.
هنگام کار با گیرنده های رویداد و کد دیگر که مراجع شیرپوینت اقلام لیست از طریق مدل شی, من اغلب مرتکب اشتباه می شوند که تولید این خطا در زمان اجرا:
خطا در بارگذاری و در حال اجرا رویداد Conchango.xyzzyEventReceiver گیرنده در xyzzy, نسخه = 1.0.0.0, فرهنگ = بی طرف, PublicKeyToken = 0dc50a750396c3ac. Additional information is below. : Value does not fall within the expected range.
I think this is a fairly generic error that is potentially caused many different ways. اما, one simple explanation is that I’m referencing a field incorrectly. If the name of the field is "Due Date", من باید آن را مانند این در گیرنده رویداد مرجع:
properties.ListItem["Due Date"]
وقتی که من املای غلط و یا استفاده از مورد اشتباه در هنگام اشاره به زمینه, SharePoint generates the above mentioned runtime error. مثلا, این اشتباه است:
properties.ListItem["due Date"]
</پایان>
We can, should and do create many views in SharePoint lists (کتابخانه های اسناد, لیست های سفارشی, غیره). SharePoint always lists available views in alphabetical order. We cannot change this using out of the box functionality. If it can be done via customization (and I’m not sure it can), it’s far to technical for your typical end user.
If you want to control the order in which SharePoint lists available views, simply prepend a number or letter to the view name, همانطور که در:
1 – By Material Type
2 – All Documents
3 – Due Date-یا-
A – By Material Type
B – All Documents
C – Due Date
I have also created views whose purpose is strictly to feed a KPI. I have been following this naming convention:
Z_KPI_[شرح]
That causes my "KPI" views to appear at the bottom of the list.
</پایان>
به عنوان یک پدر و مادر, somewhere along the line I discovered the "When I was a little boy" trick.
پسر من, احتمالا چهار یا پنج در آن زمان, بازی بالون و مانند اغلب پسر که با بالن بازی, he popped it. He was very upset. The world had come to an end. I said to him, "when I was little boy, I had a balloon and it popped and eventually, I got a new balloon." It seemed to help him cope with his loss and led to a fun talk about what it was like when I was a little boy.
That worked well as a consolation technique and I used it a several times over the next period of time. I did get into trouble once when his Monster Rancher 3 creature died. I talked about how my dog, Prince, had died in a car accident. این بار, his response was, "Now I feel bad about two things!" I shied away from using the "when I was a little boy" technique for consolation after that.
Before the dead dog incident, اما, I had also started to use the technique to convince him to do chores. "When I was a little boy, I had to go out and get the newspaper", "clean my room", "get Mommy her coffee cup", غیره.
This too was pretty successful for a while, but he started to increasingly rebel against the tyranny of my childhood. One event, in particular, marked the end. I told him to bring the garbage cans from curb back to the garage. He argued and I responded, "When I was a little boy, I had to take the garbage back to the garage." He responded, "Oh yeah! Well when you were a little boy, that was STUPID!".
</پایان>
تکمیلی (02/29/08): This new codeplex project seems to provide a method for securing individual columns: http://www.codeplex.com/SPListDisplaySetting. If you have any experience working with it, لطفا ترک یک نظر.
Forum posters frequently ask a question like this: "I have a manager view and and a staff view of a list. How do I secure the manager view so that staff can not use it?"
They also frequently ask a related question: "I want to secure a specific metadata column so that only managers may edit that column while others may not even see it."
These answers apply to both WSS 3.0 و MOSS:
There are several techniques one can follow to meet these kinds of security requirements. Here’s what I can think of:
None of those options are really that great, but there is at least a path to follow if you need to, even if it’s hard.
توجه: If you go down any of these paths, don’t forget about "Actions -> Open with Windows Explorer". You want to be sure that you test with that feature to make sure that it doesn’t work as a "back door" and defeat your security scheme.
If you have other ideas for or experiences with securing columns or views, please ایمیل من or leave a comment and I’ll update this posting as appropriate.
</پایان>
اگر شما برنامه نویسی فایل ADF و انجام تعداد زیادی از کد / واردات / تست چرخه, use the version number to make your life easier.
من نفرت را به آن اعتراف, اما تا این هفته, I was always deleting the ADF and re-importing it. This would break my business data columns and make me re-wire them. All unnecessary.
File this under "it’s obvious once you see it".
مثال:
<LobSystem
xmlns:XSI="HTTP://www.w3.org/2001/XMLSchema-instance" XSI:schemaLocation="HTTP://schemas.microsoft.com/office/2006/03/BusinessDataCatalog BDCMetadata.xsd" نوع="WebService" نسخه="1.2.0.0" نام="xyzzyDocumentReview" xmlns="HTTP://schemas.microsoft.com/office/2006/03/BusinessDataCatalog">
تغییر آن نسخه و واردات مجدد و کسب و کار موجود در ستون داده ها با استفاده از نسخه به روز شده به طور خودکار با هیچ تنظیمات اضافی مورد نیاز.
</پایان>
در من تلاش در حال ارائه ستون مراجعه مفید تر با استفاده از BDC, I hit a wall with the BDC picker. If you haven’t see it, the BDC picker is similar to a people picker except that it works with columns of type "business data".
به جمع دسترسی داشته باشید شما با کلیک کردن بر روی آیکون کتاب باز از یک ستون اطلاعات کسب و کار به عنوان نشان داده شده است:
The above image shows a business data column called "Master Document Id". That column is connected, از طریق BDC, to a web service. The web service returns two columns of information: Document ID and Title. The business purpose here is to provide a "this document is based on" تابع. Users select a "master" سند و هنگامی که آنها را ذخیره کنید, یک رویداد گیرنده کپی زمینه های متا داده ها از استاد اشاره.
به طور پیش فرض, the BDC picker looks like this when I search for a document whose ID = "38":
مفید, but not good enough. People don’t think in terms of IDs, they think in terms of titles and/or other meta data. The picker allows you to search on other columns (e.g. عنوان) اما لیستی واقعی از عناوین آن را نشان نمی دهد, فقط DocId خود را همانطور که در اینجا نشان داده شده است:
(ضربه روی صفحه نمایش خیلی بزرگ نیست چرا که من جستجو که هیچ نتایج معتبر می گرداند انتخاب نشده, اما شما می توانید ببینید که اگر آن را برخی از نتایج پیدا کرده بود, آن را فقط نشان داده DocId, نه عناوین).
I searched high and low for the answer to this and failed. My colleague, ارجمند جاناتان بنوا, had faced and solved this issue. When I reached out to him for help, او به من در مسیر درست اشاره کرد.
Configure the picker to show multiple columns via the "ShowInPicker" ملک در ADF:
<ویژگی نام="ShowInPicker" نوع="System.Boolean">درست</ویژگی>
در جزئیات بیشتر:
<!-- عنوان --> <TypeDescriptor TypeName="System.String" نام="عنوان" > <LocalizedDisplayNames> <LocalizedDisplayName LCID="1033">عنوان</LocalizedDisplayName> </LocalizedDisplayNames> <خواص> <ویژگی نام="DisplayByDefault" نوع="System.Boolean">درست</ویژگی> <ویژگی نام="ShowInPicker" نوع="System.Boolean">درست</ویژگی> </خواص> </TypeDescriptor>
Setting this property does introduce a minor problem. As soon as you set it once, you need to set it for every column you want to show. در مورد من, BDC picker showed DocId by default. اما, once I added "ShowInPicker" به عنوان, DocId no longer displayed. I solved that by explicitly setting the ShowInPicker property for Doc ID.
در اینجا نتیجه است:
(I’ll explain the odd-looking "168 – CamlSchema.xsd" construction in a future blog post. In short, این یک رشته متنی است که اجازه می دهد تا برای یک تجربه کمی بهتر کاربر).
البته, به نوشته این وبلاگ است, I just did a search for "ShowInPicker" و بازدید های متعدد, از جمله این یکی: http://msdn2.microsoft.com/en-us/library/ms583986.aspx. It explains the meaning of that property along with some other good BDC stuff.
</پایان>
به منظور کار در اطراف یک مشکل KPI من در مورد اینجا نوشت, I did some testing and discovered that KPI’s work against folders with meta data in the same way that they work against documents or list items. I proved it out by creating a new content type based on the folder content type and then added a few fields. I created some indicators and proved to myself that KPIs work as expected. This was welcome news. It’s not perfect, because the drill-down you get from the KPI against the folders is not exactly what you want. This isn’t too much a drawback in my case because 1) کاربران نهایی نمی دانم هر بهتر و 2) the drill-down goes to a folder. They click the folder name and they are at the item. It’s two clicks instead of one, which isn’t the end of the world.
This flowed nicely with the work I was doing. I am creating a folder for every document that gets uploaded. This is done via an event receiver. به عنوان یک نتیجه, it’s a piece of cake to keep the parent folder’s meta data in sync with the KPI-driven meta data from the file itself since the plumbing is already in place. This allows me to have my KPI’s and eat them too 🙂
I modified the event receiver to add the folder and then set this new folder’s content type to my custom KPI-friendly content type. This bit of code did the trick:
SPFolderCollection srcFolders = targetWeb.GetFolder("Documents").SubFolders; SPFolder addedFolder = srcFolders.Add(properties.ListItem.ID.ToString());
SPContentTypeId kpiCT = جدید SPContentTypeId("0x0120002A666CAA9176DC4AA8CBAA9DC6B4039F"); addedFolder.Item["Content Type ID"] = kpiCT; addedFolder.Item.Update();
To locate the actual Content Type ID, I accessed that content type via site settings and copy/pasted it from the URL as shown:
</پایان>
من نفرت را به آن اعتراف, but I struggled with this one all day. My event receiver needs to update a field of its parent folder. This little bit shows how to do it:
خصوصی از درجه اعتبار ساقط UpdateParentFolder(SPItemEventProperties خواص)
{
SPFolder thisItemFolder = properties.ListItem.File.ParentFolder;
thisItemFolder.Item["ZZ Approval Status"] = "Good news, هر کس!";
thisItemFolder.Item.Update();
} // UpdateParentFolder
در این مورد, I’m working with a document library and the properties are coming from an ItemAdded event.
The trick is that you can’t get the SPFolder of the item directly from the item itself (i.e. properties.ListItem.Folder is null). در عوض, go to the list item’s associated File and get the File’s folder.
</پایان>
I’m sure I’m not the first person to come up with this. اما, I haven’t noticed anyone publish a trick like this since I started paying close attention to the community last July. پس, من فکر کردم من می خواهم آن را آسان و سریع اشکال زدایی نوک ارسال.
من کار بر روی یک گیرنده رویداد آغاز شده است که برای تولید این خطا در 12 کندو:
خطا در بارگذاری و در حال اجرا رویداد Conchango.xyzzyEventReceiver گیرنده در xyzzy, نسخه = 1.0.0.0, فرهنگ = بی طرف, PublicKeyToken = blahbalhbalh. Additional information is below. : مرجع شی به یک نمونه از یک شی تنظیم نشده.
I didn’t know where I had introduced this bug because I had done too many things in one of my code/deploy/test cycles.
من سعی کردم این راه حل به PDB من در آن وجود دارد با این امید که شیرپوینت 12 کندو ردیابی پشته را نشان می دهد, اما هیچ شانس. I don’t know if it’s possible and if someone does, لطفا اجازه دهید من می دانم 🙂
من می دانم که این امکان وجود دارد نوشتن پیام های ورود به سیستم خود را به 12 کندو. Frankly, من می خواستم چیزی کمی کمتر ترسناک و سریعتر برای پیاده سازی.
آن را به من رخ داده است که من می توانم حداقل برخی از اطلاعات اولیه اثری با فیلم برداری و دوباره پرتاب استثنا کلی مثل این:
امتحان { UpdateEditionDate(خواص); } گرفتن (استثنا الکترونیکی) { پرتاب جدید استثنا("Dispatcher, UpdateEditionDate(): استثنا: [" + e.ToString() + "]."); }
این نشان داد در 12 کندو thusly:
خطا در بارگذاری و در حال اجرا رویداد Conchango.xyzzyEventReceiver گیرنده در xyzzy, نسخه = 1.0.0.0, فرهنگ = بی طرف, PublicKeyToken = blahblahblah. Additional information is below. : اعزام کننده, UpdateEditionDate(): استثنا: [System.NullReferenceException: مرجع شی به یک نمونه از یک شی تنظیم نشده. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(خواص SPItemEventProperties) at Conchango.xyzzyManagementEventReceiver.Dispatcher(خواص SPItemEventProperties, eventDescription رشته)].
که به من تمام جزئیات مورد نیاز برای پیگیری کردن آن مشکل خاص و من انتظار دارم به استفاده از آن را بسیار رفتن به جلو.
</پایان>
