Monthly Archives: Nóvember 2007

Þú getur ekki slá Náðu Sharepoint er

1 Svara

Síðustu tvo daga, I have participated in two meetings during which we presented the results of a SharePoint project. The CIO and his team joined the first meeting. That’s standard and not especially notable. The IT department is obviously involved in an enterprise rollout of any technology project. The second meeting expanded to include a V.P. frá markaðssetningu, nokkrir stjórnendur fulltrúi HR, Logistics, Framleiðsla, Capital Verkefni, Gæði, Innkaupastjóri, Þróunarsvið og aðrar deildir (sumir hverjir voru ekki einu sinni beinan þátt í núverandi áfanga). That’s a mighty wide audience.

Í fyrri líf mitt, I primarily worked on ERP and CRM projects. They both have a fairly wide solution domain but not as wide as SharePoint. To be fully realized, SharePoint projects legitimately and necessarily reach into every nook and cranny of an organization. How many other enterprise solutions have that kind of reach? Not many.

SharePoint clearly represents an enormous opportunity for those of us fortunate enough to be in this space. It provides a great technical opportunity (sem er einhvern veginn snúið á haus hér under "Technologies You Must Master"). But even better, SharePoint exposes us to an extensive and wide range of business processes through these engagements. How many CRM specialists work with the manufacturing side of the company? How many ERP consultants work with human resources on talent acquisition? SharePoint exceeds them both.

Eins og ekkert, það er ekki fullkominn, en það er fordæmdur góður staður til að vera.

Fyrir kærleika [fylla í flestum elskaði mann þinn / hærra vera], don’t change the ‘Title’ síða dálk.

7 Svör

On the SharePoint forums, someone occasionally asks about "changing the label of Title" or about "removing title from lists".

Neðsta lína: Ekki gera það!

Því miður, The notandi tengi gerir aðra leiðina breytingu á þeim dálki merki eins og sýnt:

mynd

Title is a column associated with the "Item" efnisgerð. Margir, margir, many CT’s use this column and if you change it here, it ripples out everywhere. There’s a good chance that you didn’t intend for that to happen. You were probably thinking to yourself, "I have a custom lookup list and ‘Title’ just doesn’t make sense as a column name, so I’m going to change it to ‘Status Code’ and add a description column." But if you follow through on that thought and rename ‘Title’ to ‘Status Code’, every list’s title (including document libraries) changes to "Status Code" and you probably didn’t intend for that to happen.

The real problem is that this is a one-way change. The UI "knows" that "title" is a reserved word. Svo, if you try and change "Status Code" back to "Title", it will prevent you and now you’ve painted yourself into a corner using paint that never dries 🙂

So what happens if you already changed it? I haven’t seen the answer we all want, which is a simple and easy method to change the label back to ‘Title’. Right now, the best advice is to change it to something like "Doc/Item Title". That’s a generic enough label that may not be too jarring for your users.

I have few other ideas which are on my to-do list of things to research:

  • Contact Microsoft.
  • Do something with the object model, maybe in conjunction with a feature.
  • Figure out the database schema and manually update SQL. (You should contact Microsoft before doing this though; it will likely void your support contract).

If anyone knows how to solve this, vinsamlegast staða a athugasemd.

Update late afternoon, 11/15: I found this link that describes a method for creating a type of list that does not have a title column: http://www.venkat.org/index.php/2007/09/03/how-to-remove-title-column-from-a-custom-list/

BDC ADF og vinur þinn, CDATA

1 Svara

I’ve noticed some awkward and unnecessary hand-encoding of RdbCommandText in some examples (including MSDN documentation).

I wanted to point out to newcomers to BDC that commands can be wrapped inside a CDATA tag in their "natural" form. Svo, this awkward construction:

<Eign Nafn="RdbCommandText" Tegund="System.String">
  SELECT dbo.MCRS_SETTLEMENT.id, dbo.MCRS_SETTLEMENT.settlement from dbo.MCRS_SETTLEMENT 
    HVAR (id &GT;= @MinId) AND (id &lt;= @ MaxId)
</Eign>

can be better represented this way:

<Eign Nafn="RdbCommandText" Tegund="System.String">
<![CDATA[
 SELECT dbo.MCRS_SETTLEMENT.id, dbo.MCRS_SETTLEMENT.settlement from dbo.MCRS_SETTLEMENT
HVAR (id >= @MinId) AND (id <= @MaxId)
]]>
</Eign>

</enda>

BDC Primer

Intro to BDC

Functional Dæmi: BDC ADF sem tengist SQL gagnagrunn með embed in notandi persónuskilríki og lykilorð

4 Svör

I needed to wire up MOSS to a SQL database via BDC. For testing/POC purposes, I wanted to embed the SQL account user id and password in the ADF. Starting with Þessi sniðmát (http://msdn2.microsoft.com/en-us/library/ms564221.aspx), Ég var að stofna ADF sem tengist tiltekinni SQL Server dæmis og skráir sig með ákveðna notandi persónuskilríki og lykilorð og sýnt í þessari runu:

  <LobSystemInstances>
    <LobSystemInstance Nafn="ClaimsInstance">
      <Eiginleikar>
        <Eign Nafn="AuthenticationMode" Tegund="System.String">Passthrough</Eign>
        <Eign Nafn="DatabaseAccessProvider" Tegund="System.String">SQLServer</Eign>
        <Eign Nafn="RdbConnection Data Source" Tegund="System.String">Raunveruleg miðlara  raunverulegt dæmi</Eign>
        <Eign Nafn="RdbConnection Byrjunar Vöruflokkar" Tegund="System.String">Raunveruleg fyrstu verslun</Eign>
        <Eign Nafn="RdbConnection Innbyggt Öryggi" Tegund="System.String">SSPI</Eign>
        <Eign Nafn="RdbConnection samnýtingu" Tegund="System.String">ósatt</Eign>

        <!-- Þetta eru helstu gildi: -->
        <Eign Nafn="RdbConnection Notandanafn" Tegund="System.String">actual Notandanafn</Eign>
        <Eign Nafn="RdbConnection Lykilorð" Tegund="System.String">Raunveruleg Lykilorð</Eign>
        <Eign Nafn="RdbConnection Trusted_Connection" Tegund="System.String">ósatt</Eign>

      </Eiginleikar>
    </LobSystemInstance>
  </LobSystemInstances>

Það er ekki bestu starfshætti, but it’s useful for a quick and simple configuration for testing. This was surprisingly difficult to figure out. I never found a functional example with search keywords:

  • ADF embed UserId og lykilorð
  • embed notandi persónuskilríki og lykilorð í ADF
  • embed notandi persónuskilríki og lykilorð í ADF BDC
  • SharePoint BDC grunnur
  • SharePoint Fella notandi persónuskilríki og lykilorð í ADF

</enda>

Gerast áskrifandi að bloggið mitt.

SPD sérsniðna Workflow aðgerðir — band meðferð aukahluti

1 Svara

Um viku síðan, I started up a codeplex project that provides a simple and reasonably generic method for adding custom action functions to SharePoit Designer workflow. It’s described here: http://www.codeplex.com/spdwfextensions. Beyond simply providing a framework, it also aims to provide a set of useful functions that will make SPD more useful/flexible/powerful.

Here are the current planned features for version 1.0: https://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=spdwfextensions&ReleaseId=8280

If anyone has any interest in this project, please leave a comment or start/add to a discussion here: http://www.codeplex.com/spdwfextensions/Thread/List.aspx

Here are the current set of functions that have been coded (though not fully tested as of 11/08/07):

Virka Lýsing (ef ekki sama og. Hreinar virka)
NUM-færslur() Skilar fjölda "færslur" in a string as per a specified delimiter.

Til dæmis: Num-entries in a string "a,B,c" with delimiter "," = 3.

Entry() Returns the nth token in a string as per a specified delimiter.
Lengd String.Length
Skipta() String.Replace()
Inniheldur() String.Contains()
Returns the word "true" or the word "false".
Hlutstreng(byrja) String.Substring(byrja)
Hlutstreng(byrja,enda) String.Substring(byrja,enda)
ToUpper() String.ToUpper()
ToLower() String.ToLower()
StartsWith() String.StartsWith()
Returns the word "true" or the word "false".
EndsWith() String.EndsWith()
Returns the word "true" or the word "false".

Quick & auðvelt url Encoding skrifborð gagnsemi

3 Svör

Ég hef verið að þurfa að url-umrita sumir strengi í þessari viku og löðrungur saman aa lítið tól sem ég hélt að ég myndi setja upp á SkyDrive fyrir samfélagið.

Fáðu tvöfaldur hér: http://cid-1cc1edb3daa9b8aa.skydrive.live.com/self.aspx/SharePoint/WinUrlEncode.zip

Fáðu Visual Studio lausn hér: http://cid-1cc1edb3daa9b8aa.skydrive.live.com/self.aspx/SharePoint/WinUrlEncodeVS2005.zip

Hér er skjámynd:

mynd

Fljótur og þægilegur: Fella inn tengil inn gögn view Web Part XSLT

6 Svör

UPDATE (01/17/08): Þetta blogg viðræður færslu um meira tengil XSL gæsku: http://www.sharepointsecurity.com/blog/sharepoint/sharepoint-2007-development/rewriting-links-in-search-results-xslt.

Yfirlit og Markmið: I had created a simple bar chart to serve as component on a dashboard. I’ll save the details on building charts for another post, en ég vissi ekki finna það tækni (né spurningarmerki, fyrir þessi efni). It turned out there was a bug in the chart and while I fixed that, I took the opportunity to convert some labels into hyperlinks that pointed at the underlying list behind the graph. Til dæmis, there is a label with value "Hold". I wanted to turn the label into a hyperlink so that the user could click on it and drill down to the specific entries in the list whose status value is "Hold".

Steps:

  1. Nota Visual Studio fyrir SharePoint-meðvitaðir IntelliSense.
  2. Afritaðu DVWP er XSLT inn í Visual Studio (búa til auðan verkefni, bæta XSL skrá til verkefnisins).
  3. Afrita á tengilinn sem þú vilt nota í klemmuspjald.
  4. Límdu hana í réttum stað í XSL.
  5. Convert URL argument separators on the query string from "&" to "&magnara;"
  6. Url-umrita einstakar röksemdir.
  7. Vefja sem inni <a href…> </a>

Dæmi:

Ég er með vefslóð:

HTTP://[miðlara]/[síða]/Listar / Open% 20Positions/AllItems.aspx?Skoða ={84EEA2F5-121B-40B7-946F-0FA704A1DAA1}&FilterField1 = Recruiter&FilterValue1 = Hold

Ég umbreyta það inn:

     <a href="Listar / Open% 20Positions/AllItems.aspx?Skoða =% 7b84EEA2F5-121B-40B7-946F-
0FA704A1DAA1}&magnara;FilterField1 = Recruiter&magnara;FilterValue1 = Hold">
       Halda:
     </a>

Ég hef höndunum umbreytt fyrsta rifrildi frá:

{84EEA2F5-121B-40B7-946F-0FA704A1DAA1}

að:

%7b84EEA2F5-121B-40B7-946F-0FA704A1DAA1}

(Í þetta, opinn Brace umbreytir í% 7b og lokun borsveif umbreytir í% 7D)

Annað og þriðja rök’ breytur ("FilterField1=Recruiter" and "FilterValue1=Halda" sig) þarft ekki að vera url-kóðuð vegna þess að þeir innihaldi ekki nein hættuleg stafi.

Skýringar:

Þessi tækni ætti almennt að vinna hvar sem þú vilt að embed tengil í XSLT þar tengil inniheldur breytur á slóðinni svo sem:

HTTP://[miðlara]/[síða]/Listar / Open% 20Positions/AllItems.aspx?Skoða ={84EEA2F5-121B-40B7-946F-0FA704A1DAA1}&FilterField1 = Recruiter&FilterValue1 = Hold

Ég fékk slóðina sig með aðgang að sérsniðnum lista og höndunum sía á stöðudálknum (labeled "Recruiter" ofan).

Fljótleg og einföld: Virkja SharePoint Designer workflow að uppfæra InfoPath form

Skildu eftir skilaboð

Atburðarás: I have an InfoPath form that front-ends a workflow process implemented using SharePoint Designer. At one point, a manager must approve the form. Since I cannot count on workflow history to meet my auditing requirements, Ég ákveð að geyma eigin endurskoðun skilaboð minn beint á formi sjálft.

Yfirlit:

Design the form and publish it as a efnisgerð and the form itself to a document library. Mark desired form fields as being updateable from MOSS. The form is tied to the content type and the content type is "attached" to a forms library (or many, if you want). Write a workflow that updates the field.

Specific Steps:

  1. Create a document library. This will hold your InfoPath template.
  2. Create a forms library.
  3. Create the InfoPath form. Include a text field, "Audit Message".
  4. Publish the form as a content type (NOT a document).
  5. While filling out the publishing dialogs:
    a) Save the .xsn file to the document library (stíga #1).
    B) Publish the "Audit Message" field and mark true: "Allow users to edit data in this field by using a datasheet or properties page".
    c) Create a new content type and give it an appropriate name.
  6. Access the forms library.
    a) Go to its advanced settings and enable the forms library to manage content types.
    B) Select the newly created content type (5c above). It will be grouped under "Microsoft InfoPath" (or similar).
    c) Remove the default "Form" content type from the library.
    d) Mark the library to "show as web page" so that the form will launch from SharePoint and not the InfoPath workstation client.
  7. Go back to the forms library proper and click "New" to simply verify that the form is posted correctly and acting as you want.
  8. Fire up SharePoint Designer and navigate to the site that hosts your form library (from step 2).
  9. Create a new workflow attached to the forms library.
  10. Add a single action "Set Field in Current Item". You should expect SharePoint Designer to list your your field, "Audit Message". Assign it a value.
  11. Click Finish and go back to the form library.
  12. Create a new form and put some test value into the "Audit Message" sviði.
  13. Save it and go back to the form library.
  14. Right-click, select "Workflow" and start up your workflow.
  15. It should run almost immediately. Pull up the form (from step 12) and if all has gone to plan, "Audit Message" has been assigned whatever value you provided in step 10.

Skýringar:

Not all controls may configured for this bi-directional communication. Til dæmis, it does not seem to implement an SPD workflow that modifies text fields wrapped inside repeating sections.

One of the key take-away’s here is that we’ve really created a content type with an associated template. This also enables us to store multiple InfoPath form templates in the same form library.

This requires forms server. It’s most certainly not going to work in a WSS 3.0 environment and probably even requires an Enterprise SharePoint environment.

The Beagle lentur (Október 2007 tölublað)

Skildu eftir skilaboð

(Þetta er reyndar svolítið gamall fréttir, en eins og uppáhalds eldur stöð einkunnarorð mín kunngerir, "Better late than never").

Stöðva það út hér: http://www.sharepointbeagle.com/

Ef þú hefur ekki nú þegar, be sure to sign up.

Auðvitað, be sure to read minn hlutur about a real-world SharePoint project (þ.mt kröfur skilgreiningu, Er KPI, efnisgerðir, dashboards and more) as well as my colleague’s article about the content query web part.

There’s lot of other good stuff too.

Hvernig á að fjarlægja “Skoða allt innihald vefsvæðis” hlekkur

Skildu eftir skilaboð

Ég spurði þessa spurningu næstum í hverri viku, venjulega í tengslum við öryggi umræðu. An administrator/site creator has provisioned a site, stilla öryggi, arranged web parts and customized the quick launch to provide that oh-so-perfect set of options to the end user. En, út af the kassi, you can’t remove the "view all site content" hlekkur.

Mark Wagner veitir svarið hér (http://www.crsw.com/mark/Lists/Posts/Post.aspx?ID=36). Hans skrifa-upp er frábær á tveimur stigum. Það veitir svar við spurningunni, "How do I remove the View All Site Content" hlekkur? Þá, það svarar strax eftirfylgni á spurningu: Hvernig get ég gera auðveldlega skoða öll efni á síðuna tengil á síðuna-við-síða grundvelli?

Sem bónus: Nálgun hans vinnur fyrir WSS, ekki bara MOSS.

</enda>

Gerast áskrifandi að bloggið mitt!