Quick u sempliċi: Dispożizzjoni Sit Web Uża Object Model SharePoint Fil C #

I tried searching for a little snippet code that would show how I can create a new SPWeb in a site collection. I didn’t find it as quickly or easily as I expected so I thought I’d slap together a little entry on the subject.

Dan il-kodiċi joħloq sit Wiki ġdida:

 SPSite siteCollection;

    siteCollection = ġdid SPSite("http://conchang-o9l8qi");

    SPWeb w = siteCollection.OpenWeb();

    w.Webs.Add("xyzzy", "xyzzy Title",
        "xyzzy description", 1033, SPWebTemplate.WebTemplateWIKI, falza, falza);

My initial searches failed because I was looking for phrases like "provision a web site using sharepoint object model" and the like.

Jekk inti tfittxija for "Webs.Add()", inti ser issib numru ta 'daħliet blog utli ħafna, MSDN articles and SDK documentation that go into depth on this subject. I definitely recommend dan is-sit.

</aħħar>

Abbona għall-blog tiegħi.

Tintegra flussi tax-xogħol Designer SharePoint ma Web Services

I’ve been playing around with custom actions for SharePoint Designer for some time (tara hawn for some detailed stuff, if that interests you).

Fil-proġett kurrenti tiegħi, we need to do some fairly heavy lifting and we want to use declarative SPD workflow to manage the associated business process.

Long storja qasira, this is entirely possible. I extended my Codeplex project to invoke a "helper service" and now we can invoke a web service directly from an SPD workflow.

Here’s the signature:

 pubbliku string Dispatcher(
        Guid WebID, // Passed by the runtime environment
        Guid SiteID, // Passed by the runtime environment
        string ListID, // Passed by the RTE (don't know why this is a string, not a GUID)
        int ListItemID, // Passed by the RTE.
        string XmlMessage) // Passed by the user as declared in SPD.

This leverages the fact that we can get at important workflow information, like the site, list ID, eċċ. This is well documented in several places for those of you interested in creating your own custom actions. The idea is to extract the XML string as provided by the user to dispatch an appropriate procedure. Fun stuff!

Sfortunatament, this is obviously a one-way ticket down to "Loosey Goosey" anti-pattern land, but it’s better than hitting a brick wall 🙂

Is it an anti-pattern if you do it even though you know it’s an anti-pattern?

I hope to wrap this inside Codeplex in the near future. If you’re interested in me doing so, give me poke (email or leave a comment) and I’ll be that more enthusiastic about doing it 🙂

</aħħar>

Abbona għall-blog tiegħi.

IL-ĦADD Funny: “I wonder jekk password tiegħek …”

I reċentement xtara ikla għall brother tiegħi (bħas-soltu) and we ended up talking about funny things that we did at our respective colleges. At my alma mater, Lafayette Kulleġġ, the academic support IT department had a very inclusive way about it. We were given a LOT of rope and I took advantage of that at times.

Two my favorite memories relate to my good friend, Gabe. He had made the terrible mistake of telling people his freshman year that "I’m a freshman, but I have Sophomore standing" due to the various advanced placement classes he had taken, eċċ. Many of us were similarly situated but we didn’t talk about it so much. His senior year, when we introduced him to people, we’d say "This is Gabe. He’s a Senior, but he has Sophomore standing".

The college had some Sun workstation/servers running X-Window. They had gigantic monitors and the engineers used them for CAD and other boring engineer stuff. We CS people used them to learn programming and, tal-kors, l-logħob.

Aħna ma bħall-inġiniera kompjuter hilflose għal ħafna sabiex wieħed ta 'affarijiet favoriti tagħna biex tagħmel huwa li telnet għall-kaxxa kienu fuq u run X-għajn on them. This would pop up a pair of eyes that followed the mouse around on the screen. You could pop up even more and have literally a dozen or more of the X-eye applications running. Try not to laugh out loud when a hapless engineer is trying to close X-eye after X-eye and muttering under his breath about it 🙂

We also played X-trek on those boxes. Biex tagħmel dan, you had to download the source, get various dependencies wherever you could find them and build it. I wasn’t a sophisticated C programmer, but I could read header files. I was looking through these and found directives like "#DEFINE MAX_TORPEDO_DISTANCE 10". I played around with that increase range and power for phases and torpedoes, re-built it and then destroyed Gabe the next time we played.

Gabe was also a huge fan of a TV show called Blake’s 7. I had never seen it, but that didn’t prevent me from insisting that Dr. Who is the superior show. The arguments would get heated at times 🙂

Ġurnata waħda, it occurred to me that I could probably guess his UNIX password. I sat down next to him one day and announced in a loud tone, "I’m going to guess your password right now, Gabe." "Yeah, dritt" was his answer. I then logged in, entered his user id, turned to face him, typed and said out loud, "I wonder if it’s B-L-A-K-E-7" ? Touch typing has never paid off as handsomely as it did that day.

Ġimgħa d-dieħla (or soon): More computer room antics from college.

Do you have any to share? Leave a comment or email me and I’ll publish them here.

</aħħar>

Abbona għall-blog tiegħi.

Tags:

Tħabbir Pubblika Minuri: Windows Live Sigurtà Settings u Tikkuntattja Sidien Ispazju

I receive a handful of messages from individuals via the built-in "send a message" funzjoni Microsoft tipprovdi bi spazji ħajjin (li tospita wkoll blog tiegħi) kull xahar.

Madwar terz tal-ħin, those users have secured their live spaces account such that I cannot reply. This is some kind of anti-spam feature I assume.

</aħħar>

Sempliċi Spjegazzjoni: “Valur ma taqax fi ħdan il-firxa mistennija.”

UPDATE: An anonymous poster left a great comment about internal names. Be sure to read it.

Meta taħdem ma 'riċevituri avveniment u l-kodiċi oħra li SharePoint oġġetti referenzi lista permezz tal-mudell oġġett, I spiss jagħmlu żbalji li jiġġeneraw dan l-iżball fil runtime:

Jtellgħu u jħaddmu Żball avveniment riċevitur Conchango.xyzzyEventReceiver fil xyzzy, Verżjoni = 1.0.0.0, Kultura = newtrali, 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. Madankollu, one simple explanation is that I’m referencing a field incorrectly. If the name of the field is "Due Date", Ikolli referenza hija bħal dan riċevitur avveniment:

properties.ListItem["Due Date"]

Meta I misspell jew jużaw il-każ żbaljat meta referenzar-qasam, SharePoint generates the above mentioned runtime error. Per eżempju, dan hu ħażin:

properties.ListItem["due Date"]

</aħħar>

Abbona għall-blog tiegħi.

Utent Aħħari Quick Tip: Sort Views fil Librerija ta 'Dokumenti, Lista, eċċ.

Nistgħu, għandhom u ma joħolqu ħafna ideat fil-listi SharePoint (libreriji dokument, listi tad-dwana, eċċ). 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 (u M'inix ċert li tista), huwa ferm biex teknika għall-utent tiegħek tmiem tipiku.

Jekk inti tixtieq li tikkontrolla l-ordni li fiha SharePoint jelenka fehmiet disponibbli, sempliċiment prepend numru jew ittra lill-isem fehma, kif fil-:

1 – Mill Tip Materjal
2 – Dokumenti kollha
3 – Data dovuta

-jew-

A – Mill Tip Materjal
B – Dokumenti kollha
C – Data dovuta

I have also created views whose purpose is strictly to feed a KPI. I have been following this naming convention:

Z_KPI_[deskrizzjoni]

Li tikkawża "KPI tiegħi" fehmiet li jidhru fil-qiegħ tal-lista.

</aħħar>

Abbona għall-blog tiegħi.

IL-ĦADD Funny: “Meta I kien ftit Boy”

Bħala ġenitur, somewhere along the line I discovered the "When I was a little boy" trick.

My son, probabbilment erba 'jew ħames fil-ħin, kien playing bużżieqa u simili ħafna subien ftit li jilagħbu bil blalen, 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. Din id-darba, 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, madankollu, 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", eċċ.

This too was pretty successful for a while, but he started to increasingly rebel against the tyranny of my childhood. One event, b'mod partikolari, 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!".

</aħħar>

Abbona għall-blog tiegħi.

Tags:

Fehmiet u Kolonni fuq Listi u Libreriji Dokument msemmija ma jistgħux jinkisbu

UPDATE (02/29/08): Dan il-proġett CodePlex ġdida tidher li tipprovdi metodu biex tiġi żgurata kolonni individwali: http://www.codeplex.com/SPListDisplaySetting. If you have any experience working with it, jekk jogħġbok leave kumment.

Posters forum spiss jistaqsu mistoqsija bħal dan: "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?"

Huma wkoll spiss jistaqsu mistoqsija relatata: "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 u MOSS:

  • SharePoint ma jipprovdix l-il-kaxxa ta 'appoġġ għall-iżgurar fehmiet.
  • SharePoint ma jipprovdix l-il-kaxxa ta 'appoġġ għall-kolonni tas-sigurtà.

There are several techniques one can follow to meet these kinds of security requirements. Here’s what I can think of:

  • Use out-of-the-box item level security. Views always honor item level security configuration. Event receivers and/or workflow can automate security assignment.
  • Use personal views for "privileged" fehmiet. These are easy enough to set up. Madankollu, due to their "personal" natura, these need to be configured for each user. Use standard security configuration to prevent anyone else from creating a personal view.
  • Uża parti tad-data web ħsieb u jimplimentaw xi tip ta 'sigurtà AJAXy soluzzjoni tirqim.
  • Roll stess display lista funzjonalità tiegħek u jinkorporaw sigurtà tirqim fil-livell kolonna.
  • Timmodifika l-forom dħul tad-data u l-użu JavaScript flimkien mal-mudell ta 'sigurtà biex jimplimentaw sigurtà ta' livell kolonna tirqim.
  • Use an InfoPath form for data entry. Implement column-level security trimming via web service calls to SharePoint and conditionally hide fields as needed.
  • Roll stess ASP.NET funzjoni tiegħek dħul tad-data li timplimenta livell ta 'sigurtà kolonna tirqim.

Ebda wieħed minn dawn l-għażliet huma verament li kbir, iżda hemm mill-inqas triq biex isegwu jekk inti għandek bżonn, anki jekk huwa diffiċli.

NOTA: Jekk inti jinżlu kwalunkwe minn dawn mogħdijiet, 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" u defeat iskema tas-sigurtà tiegħek.

Jekk għandek ideat oħra għal jew esperjenzi bil-kolonni jew il-veduti iżgurar, jekk jogħġbok email me jew leave kumment u jien ser taġġorna dan kollokament kif xieraq.

</aħħar>

Abbona għall-blog tiegħi.

Tip Quick: BDC Numri Verżjoni ADF Are Friend Your

Jekk int idejn kodifikazzjoni fajls ADF u jagħmlu ħafna tal-kodiċi / importazzjoni / test ċikli, use the version number to make your life easier.

Ddejjaqni li jammettu li, imma sakemm din il-ġimgħa, 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".

Eżempju:

<LobSystem
xmlns:XSi="http://www.w3.org/2001/XMLSchema-instance" XSi:schemaLocation="http://schemas.microsoft.com/office/2006/03/BusinessDataCatalog BDCMetadata.xsd" Tip="Webservice" Verżjoni="1.2.0.0" Isem="xyzzyDocumentReview" xmlns="http://schemas.microsoft.com/office/2006/03/BusinessDataCatalog">

Bidla li verżjoni u ri-importazzjoni u l-kolonna data negozju eżistenti tuża l-verżjoni aġġornata awtomatikament bl-ebda konfigurazzjoni addizzjonali meħtieġa.

</aħħar>

Abbona għall-blog tiegħi.

Tags:

Soluzzjoni: Picker BDC Shows Waħda Biss Kolonna Of Riżultati

In my on-going attempts at providing a more useful lookup column using 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".

You access the picker by clicking on the open book icon of a business data column as shown:

immaġni

The above image shows a business data column called "Master Document Id". That column is connected, via 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" funzjoni. Users select a "master" document and when they save, an event receiver copies meta data fields from the referenced master.

By default, the BDC picker looks like this when I search for a document whose ID = "38":

clip_image002

That’s helpful, 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. Titolu) but won’t show the actual list of titles it found, just their DocId’s as shown here:

clip_image002[1]

(The screen shot isn’t so great because I didn’t pick a search that returns any valid results, but you can see that if it had found some results, it would only have shown DocId’s, not titles).

I searched high and low for the answer to this and failed. Kollega tiegħi, the venerable Jonathan Bradshaw, had faced and solved this issue. When I reached out to him for help, he pointed me in the right direction.

Configure the picker to show multiple columns via the "ShowInPicker" property in the ADF:

<Proprjetà Isem="ShowInPicker" Tip="System.Boolean">vera</Proprjetà>

In more detail:

  <!-- Titolu -->
  <TypeDescriptor TypeName="System.String" Isem="Titolu" >
    <LocalizedDisplayNames>
      <LocalizedDisplayName LCID="1033">Titolu</LocalizedDisplayName>
    </LocalizedDisplayNames>
    <Properties>
      <Proprjetà Isem="DisplayByDefault" Tip="System.Boolean">vera</Proprjetà>
      <Proprjetà Isem="ShowInPicker" Tip="System.Boolean">vera</Proprjetà>
    </Properties>
  </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. Fil-każ tiegħi, BDC picker showed DocId by default. Madankollu, once I added "ShowInPicker" to Title, DocId no longer displayed. I solved that by explicitly setting the ShowInPicker property for Doc ID.

Here is the result:

immaġni

(I’ll explain the odd-looking "168 – CamlSchema.xsd" construction in a future blog post. In short, it’s a concatenated string that allows for a slightly better user experience).

Of course, having written this blog entry, I just did a search for "ShowInPicker" and found numerous hits, including this one: http://msdn2.microsoft.com/en-us/library/ms583986.aspx. It explains the meaning of that property along with some other good BDC stuff.

</aħħar>

Abbona għall-blog tiegħi!

Tags: