Arkivji ta 'Kull Xahar: Novembru 2007

MOSS jgħidlekx Me My Isem Kolonna huwa Riservat jew użat … Imma din mhix

Ħalli Risposta

UPDATE 12/04/07: Ara this Microsoft KB (http://support.microsoft.com/kb/923589) għal informazzjoni relatata.

Attwalment, jirriżulta huwa, iżda tricksy MOSS had to make it difficult.

My customer does some development work on his MOSS site over the weekend. It’s a bit of a jumble as to what he actually did, imma r-riżultat aħħari huwa dan:

  • He tries to add a site column called "Quantity" and MOSS replies: "The column name that you entered is already in use or reserved. Choose another name."
  • He attempts to add it to another environment and that works. Għalhekk, "Quantity" is not a reserved name.
  • He tries to find an existing site column named "Quantity" in that site collection. He cannot find it.

I did some research, and even some coding, waxed philosophical and finally found that a column named Quantity did, fil-fatt, exist. It was in the "_Hidden" group. Hence, we could not find it via the SharePoint user interface.

How did it get there? I do not know, but I have a theory (or as my wife would call it, "blah blah blah"). X'imkien matul il-linja, a fabulous forty template was added and probably activated at a site in the site collection. It was then deactivated (or the site removed). The site column, madankollu, remained but in the "_Hidden" group. If someone knows better, please let me know via email or post in the comments.

SharePoint was telling the truth. It’s hardly worth pointing out that that message is not as helpful as it could be. It would be nice to see that message fork into two different messages in the future: 1) Say that the column name is reserved or it is not. 2) If it’s not reserved, show the site, or at least the group, where the column name is already used.

</aħħar>

Data Preżenti Via-Lista Custom OM (jew, Énième OM Data Displayor [bħal Yacc, imma differenti])

Ħalli Risposta

Illum, I spent a handful of hours tracking down the root cause behind the message "The column name that you entered is already in use or reserved. Choose another name."

Il-kolonna in kwistjoni jistgħu jinħolqu, imħassra u maħluqa mill-ġdid fl-ambjent ieħor, so I knew it wasn’t a reserved name. Madankollu, I simply couldn’t find the column anywhere via the standard SharePoint user interface at any site in the site collection.

I posted to MSDN forums here and the indomitable Andrew Woodward pointed me in the direction of the underlying object model data.

I went off to codeplex to find some tools that would help me peer into the underlying OM data and help me locate the trouble.

I tried several tools and they were very cool and interesting but in the end, the UI wasn’t good enough for my purpose. I’m not criticizing them by any means, but clearly the tool-makers didn’t have my problem in mind when they created their UI :). Most people seem to be investing a fair amount of time and effort in creating workstation / client applications that provide tree views, right-click context menus and so forth. These are nice and all, but it’s a lot of work to create a top-of-the-line user experience that is also very flexible.

I really needed an answer to this problem. It occurred to me that if I could get all of the site columns in the site collection into a custom list, I could filter, sort and create views that would help me find this supposedly existing column (which it did, BTW). I went ahead and did that and an hour or two later, had all my site columns loaded into a custom list with grouping, sorting and so forth. I found my answer five minutes later.

If and when I successfully take over the world, I think I will decree that all SharePoint tools providers must seriously consider surfacing their object model data in a custom list. That way, I have the power to search any way I want (constrained, tal-kors, by standard sharepoint features).

SharePoint Designer Workflow Custom Azzjoni — Osservazzjoni About <Tie qasam Designer Tip =”StringBuilder” … />

1 Irrispondi

Just a quick osservazzjoni li hemm differenza importanti ħafna bejn dawn iż-żewġ definizzjonijiet:

<FieldBind Field="InParam1" DesignerType="StringBuilder" Id="2" Text="Input parameter #1"/>

versus:

<FieldBind Field="InParam1" Id="2" Text="Input parameter #1"/>

L-ewwel turi bħal dan fil SPD:

immaġni

filwaqt li dawn tal-aħħar turi bħal dan:

immaġni

I’m not sure how helpful these screen shots are but I put in the effort to make them so you have to view them 🙂

L-osservazzjoni hija din: StringBuilder jippermettilek li tibni string (ovvjament) billi jitħalltu flimkien Literali b'Sensiela u data workflow (via the "Add Lookup" buttuna fil-rokna tax-xellug t'isfel). When you use the Add Lookup button, it inserts a token in the form "[%token%]". When SharePoint invokes your custom action, (C # kodiċi fil-każ tiegħi), SharePoint jgħaddi l-token innifsu, not the value of the token. If you use the default designer type (it-tieni tip), SharePoint tespandi l-token u jgħaddi valur attwali tal-token għal azzjoni tiegħek.

StringBuilder = BAD, tip disinjatur default = TAJBA.

Of course, that’s not what I really mean. Just don’t try and pass a parameter to your custom action when the designer type = StringBuilder. Use the default designer type and chain a StringBuilder to it up front if you need to build complex strings in your workflow (li inċidentalment huwa eżattament dak li wieħed ma toħloq suġġett dinamiku għall-azzjoni email, iżda li suġġett għad-dħul ieħor blog, għandha l-).

<aħħari />

Prematur Attivazzjoni Workflow — Soluzzjoni A Non-mediku

8 tweġibiet

UPDATE: Ara din id-diskussjoni MSDN, speċjalment l-aħħar dħul: http://forums.microsoft.com/MSDN/showpost.aspx?postid=2631057&siteid=1. It describes a condition that may short circuit this whole thing. In short, jista 'jkun sempliċi bħala teħid mill-inqas wieħed mill-oqsma obbligatorji.

I jkollhom librerija dokument li jappoġġja tmien tipi ta 'kontenut.

I have a SharePoint Designer workflow that wants to calculate and assign a "reminder date" by simply subtracting 30 days from another column, "due date". This should only happen for one of the content types, "Insurance". The business objective is to produce a KPI that shows two categories of insurance documents: "about to expire" and "expired." (You can read more about this kind of KPI and more substantial drill-down hawn).

I have configured the workflow to fire when a new item is created and when an item is modified. The idea is that when an insurance document is uploaded, we calculate a "warning date" based on the expiration date. A pair of views work in connection with a KPI List to highlight these conditions when users hit their home page.

This strategy does not work when I upload a document.

I upload the document and I am presented with the meta data entry screen. F'dan il-punt, I’m already in trouble. SharePoint has already, prematurely from my perspective, fired the workflow. I haven’t had a chance to pick the correct content type nor assign a due date. Fl-istess ħin, the workflow does not fire when I hit the submit button at this time. There’s some built-in logic that "believes" that first submit is part of the "create" event. Allura … my workflow has fired and when it executed, it was passed default meta data values.

The best work-around I know of is to insert a "pause until" activity in the workflow. I have the workflow pause for 1 minute. While it’s pausing, I select the correct content type, enter the meta data and submit. The pause completes and the workflow proceeds as needed. (Note that in my environment, timer workflow activities from SPD do not work out of the box. You may have the same trouble. Ara hawn for more details).

I don’t like "magic delay" work-around. What happens if the user uploads a document and the phone rings and the ensuing conversation outlasts the pause? I can make the pause longer, but I still don’t like it.

I wrote about this on the MSDN forums here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2430725&SiteID=1

SharePoint Sigurtà Fundamentals Ewwel / Evita nases Komuni

8 tweġibiet

UPDATE 12/18/07: Ara l-artikolu Paul Liebrand għall xi konsegwenzi tekniċi tat-tneħħija jew timmodifika l-ismijiet tal-grupp default (Ara l-kumment tiegħu hawn taħt kif ukoll).

Ħarsa ġenerali:

SharePoint security is easy to configure and manage. Madankollu, it has proven to be difficult for some first-time administrators to really wrap their hands around it. Not only that, I have seen some administrators come to a perfect understanding on Monday only to have lost it by Friday because they didn’t have to do any configuration in the intervening time. (I admit to having this problem myself). This blog entry hopefully provides a useful SharePoint security primer and points towards some security configuration best practices.

Important Note:

This description is based on out of the box SharePoint security. My personal experience is oriented around MOSS so there may be some MOSS specific stuff here, but I believe it’s accurate for WSS. I hope that anyone seeing any errors or omissions will point that out in comments or email me. I’ll make corrections post haste.

Fundamentals:

For the purposes of this overview, there are four fundamental aspects to security: users/groups, securable objects, permission levels and inheritance.

Users and Groups break down to:

  • Individual users: Pulled from active directory or created directly in SharePoint.
  • Groups: Mapped directly from active directory or created in SharePoint. Groups are a collection of users. Groups are global in a site collection. They are never "tied" to a specific securable object.

Securable objects break down to at least:

  • Sites
  • Document libraries
  • Individual items in lists and document libraries
  • Folders
  • Various BDC settings.

There other securable objects, but you get the picture.

Permission levels: A bundle of granular / low level access rights that include such things as create/read/delete entries in lists.

Inheritance: By default entities inherit security settings from their containing object. Sub-sites inherit permission from their parent. Document libraries inherit from their site. So on and so forth.

Users and groups relate to securable objects via permission levels and inheritance.

The Most Important Security Rules To Understand, Ever 🙂 :

  1. Groups are simply collections of users.
  2. Groups are global within a site collection (I.E. there is no such thing as a group defined at a site level).
  3. Group name not withstanding, groups do not, in and of themselves, have any particular level of security.
  4. Groups have security in the context of a specific securable object.
  5. You may assign different permission levels to the same group for every securable object.
  6. Web application policies trump all of this (see below).

Security administrators lost in a sea of group and user listings can always rely on these axioms to manage and understand their security configuration.

Common Pitfalls:

  • Group names falsely imply permission: Barra mill-kaxxa, SharePoint defines a set of groups whose names imply an inherent level of security. Consider the group "Contributor". One unfamiliar with SharePoint security may well look at that name and assume that any member of that group can "contribute" to any site/list/library in the portal. That may be true but not because the group’s name happens to be "contributor". This is only true out of the box because the group has been provided a permission level that enables them to add/edit/delete content at the root site. Through inheritance, the "contributors" group may also add/edit/delete content at every sub-site. One can "break" the inheritance chain and change the permission level of a sub-site such that members of the so-called "Contributor" group cannot contribute at all, but only read (per eżempju). This would not be a good idea, ovvjament, since it would be very confusing.
  • Groups are not defined at a site level. It’s easy to be confused by the user interface. Microsoft provides a convenient link to user/group management via every site’s "People and Groups" rabta. It’s easy to believe that when I’m at site "xyzzy" and I create a group through xyzzy’s People and Groups link that I’ve just created a group that only exists at xyzzy. That is not the case. I’ve actually created a group for the whole site collection.
  • Groups membership does not vary by site (I.E. it is the same everywhere the group is used): Consider the group "Owner" and two sites, "HR" and "Logistics". It would be normal to think that two separate individuals would own those sites — an HR owner and a Logistics owner. The user interface makes it easy for a security administrator to mishandle this scenario. If I didn’t know better, I might access the People and Groups links via the HR site, select the "Owners" group and add my HR owner to that group. A month later, Logistics comes on line. I access People and Groups from the Logistics site, add pull up the "Owners" group. I see the HR owner there and remove her, thinking that I’m removing her from Owners at the Logistics site. Fil-fatt, I’m removing her from the global Owners group. Hilarity ensues.
  • Failing to name groups based on specific role: The "Approvers" group is a perfect example. What can members of this group approve? Where can they approve it? Do I really want people Logistics department to be able to approve HR documents? Of course not. Always name groups based on their role within the organization. This will reduce the risk that the group is assigned an inappropriate permission level for a particular securable object. Name groups based on their intended role. In the previous HR/Logistics scenario, I should have created two new groups: "HR Owners" and "Logistics Owners" and assign sensible permission levels for each and the minimum amount required for those users to do their job.

Other Useful References:

If you’ve made it this far:

Please let me know your thoughts via the comments or email me. If you know other good references, please do the same!

Quick u Easy: Oħloq Data View Web Parti (DVWP)

2 tweġibiet

Hemm minjiera ta 'informazzjoni kbir fuq il-WSS 3.0 Data View Web Parti (DVWP) on the web from several sources. Madankollu, I found it to be surprisingly difficult to find information on this first very basic step. Here is another article in the "quick and easy" serje jindirizzawha.

Segwi dawn il-passi biex toħloq parti tad-data web ħsieb (DVWP). They are based on an "Announcements" parti web, iżda tapplika għal-listi aktar.

  1. Oħloq parti web Avviżi u iżżidhiex għal sit.
  2. Iftaħ is-sit SharePoint Designer.
  3. Iftaħ-sit default.aspx.
  4. Select the Announcements web part and right-click.
  5. Mill-menu kuntest, select "Convert to XSIl-T Data View".

SharePoint Designer javżak li dan is-sit issa huwa customised mid-definizzjoni sit tagħha. Li mhux neċessarjament ħażin, iżda hemm implikazzjonijiet importanti (prestazzjoni, upgrade, oħrajn) which are beyond the scope of this little "Quick and Easy" dħul. To get more information on this subject, I jirrakkomandaw żewġ kotba hawn kif ukoll tfittxija tiegħek Internet favoriti.

Ikkonferma li inti ma kien korrett:

  1. Agħlaq u terġa tiftaħ il-web browser (to avoid accidentally re-posting the original "add a new web part").
  2. Select the web part’s arrow drop-down and choose "Modify Shared Web Part" mill-menu.
  3. Il-bord għodda jiftaħ lejn il-lemin.
  4. Il-bord inbidel minn għażliet tagħha sett normali għal dan:
immaġni

“Ma tistax tikseb l schema lista proprjetà kolonna mil-lista SharePoint” — Deskrizzjoni / xogħol-arounds

4 tweġibiet

Din il-ġimgħa, aħna finalment riprodotti problema li kienu ġew irrappurtati minn utent remot: Meta hi ppruvaw li jesportaw il-kontenut ta 'kalendarju li jisbqu, affarijiet jidher li tibda taħdem, iżda mbagħad Excel se pop up żball: "Cannot get the list schema column property from the SharePoint list". She was running office 2003, windows XP and connecting to MOSS.

I mfittxa l-internets u raw xi spekulazzjoni imma xejn 100% definitive. Hence, din il-kariga.

Il-problema: Jesportaw ħsieb li jisbqu li fih id-data (data =-tip data tal-kolonna).

Dak li ħadem għalina: Convert the date to a "single line of text". Imbagħad, jikkonvertu lura għal data.

That solved it. It was nice to see that the conversion worked, attwalment. It was quite nervous that converting things this way would fail, but it did not.

Dan bug għandu jintefa 'dell enormi fuq it-tip data data fil-moħħ tal-klijent, hekk aħna qed tmur biex tkun jfittxu risposta definittiva mill-Microsoft u nisperaw I ser post u taġġorna hawn fil-perjodu qasir ta 'żmien li jmiss bit-tweġiba uffiċjali tagħhom u l-informazzjoni hotfix.

Referenzi oħrajn:

http://www.kevincornwell.com/blog/index.php/cannot-get-the-list-schema-column-property-from-the-sharepoint-list/

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2383611&SiteID=1

<aħħar>

Abbona għall-blog tiegħi.

Quick u sempliċi: Ibgħat email bl hyperlink inkorporati mill workflow Disinjatur SharePoint

Ħalli Risposta

Darba jew darbtejn fix-xahar, xi ħadd postijiet ta 'kwistjoni forum: "How do I include hyperlinks to URL’s that are clickable from a SharePoint Designer email?"

Ippreżentat mingħajr aktar kummenti: (ukoll, attwalment hemm aktar kummenti wara l-immaġni):

immaġni

Becky Isserman ġej bi spjegazzjoni utli dwar kif ssodata link għal oġġett fil-email: http://www.sharepointblogs.com/mosslover/archive/2007/11/20/addition-to-paul-galvin-s-post-about-sending-an-e-mail-with-hyperlinks-in-spd.aspx

New rilaxx: Workflow Estensjonijiet SharePoint Designer (manipulazzjoni funzjonijiet spag)

5 tweġibiet

UPDATE: Ara hawn għal ħsibijiet tiegħi fuq il-kummerċjalizzazzjoni dan il-proġett: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!569.entry

Stajt ġew busy jaħdmu fuq proġett Codeplex tiegħi li bħalissa ffokati fuq li jipprovdu estensjonijiet manipulazzjoni spag għall flussi tax-xogħol maħluqa permezz Disinjatur SharePoint.

Ara hawn għal aktar dettalji:

Dar Proġett: http://www.codeplex.com/spdwfextensions

Rilaxx: https://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=spdwfextensions&ReleaseId=8280

Verżjoni 1.0 jinkludi l-karatteristiċi ġodda li ġejjin:

Funzjoni Deskrizzjoni (jekk mhux istess. funzjoni Net)
Num-entrati() Denunzji il numru "dħul" in a string as per a specified delimiter.

Per eżempju: Num-reġistrazzjonijiet fi string "a,b,c" ma delimetru "," = 3.

Dħul() Returns the nth token in a string as per a specified delimiter.
Tul String.Length
Ibdel() String.Replace()
Fih() String.Contains()
Denunzji-kelma "vera" jew il-kelma "false".
Substring(tibda) String.Substring(tibda)
Substring(tibda,tul) String.Substring(tibda,tul)
ToUpper() String.ToUpper()
ToLower() String.ToLower()
StartsWith() String.StartsWith()
Denunzji-kelma "vera" jew il-kelma "false".
EndsWith() String.EndsWith()
Denunzji-kelma "vera" jew il-kelma "false".

A żball runtime BDC spjegat

2 tweġibiet

I ikkawżat żball BDC din il-ġimgħa li jimmanifesta ruħu fuq l-user interface u fil- 12 doqqajs log fil runtime.

Ewwel, dan deher fil-user interface:

Ma setgħetx issib l-oqsma li tiddaħħal l-valuri Identifikatur b'mod korrett tesegwixxi MethodInstance SpecificFinder ma Isem … Tiżgura Parametri input jkollhom TypeDescriptors assoċjati ma 'kull Identifikatur definit għal dan Entità.

Hawn screen shot:

clip_image001

I tista 'wkoll toħloq dan il-messaġġ li jidhru fil- 12 log doqqajs fil-se (using my patented high-tech-don’t-try-this-at-home "Żbalji misterjuża" metodu):

11/14/2007 09:24:41.27 w3wp.exe (0x080C) 0x0B8C SharePoint Portal Server Business Data 6q4x High Exception in BusinessDataWebPart.OnPreRender: System.InvalidOperationException: Il-valur Identifikatur ”, tat-Tip ”, huwa invalidu. Expected Identifier value of Type ‘System.String’. fil Microsoft.Office.Server.ApplicationRegistry.MetadataModel.Entity.FindSpecific(Għan[] subIdentifierValues, LobSystemInstance lobSystemInstance) fil Microsoft.SharePoint.Portal.WebControls.BdcClientUtil.FindEntity(Entità Entità, Għan[] userValues, LobSystemInstance lobSystemInstance) fil Microsoft.SharePoint.Portal.WebControls.BusinessDataItemBuilder.GetEntityInstance(Ara desiredView) fil Microsoft.SharePoint.Portal.WebControls.BusinessDataDetailsWebPart.GetEntityInstance() fil Microsoft.SharePoint.Portal.WebControls.BusinessDataDetailsWebPart.SetDataSourceProperties()

I mfittxa madwar u sab xi twassal fil- MSDN forum, but they weren’t enough for me to understand what I was doing wrong. I watched a webcast by Ted Pattison li tiegħi kumpanija tkun squirreled bogħod fuq server u daħal li tirrealizza problema tiegħi.

Fil ADF tiegħi, Jien konnessjoni ma 'SQL database kif muri:

            <Proprjetà Isem="RdbCommandText" Tip="System.String">
              <![CDATA[
                TAGĦŻEL
                      , CARRIER_ID, EFFDT, Descr, EFF_STATUS, TAXPAYER_ID, NETWORK_ID, FRT_FORWARD_FLG, ALT_NAME1, ALT_NAME2, LANGUAGE_CD,
                      PAJJIŻ, Address1, ADDRESS2, ADDRESS3, ADDRESS4, BELT, NUM1, NUM2, HOUSE_TYPE, ADDR_FIELD1, ADDR_FIELD2, ADDR_FIELD3,
                      COUNTY, ISTAT, POSTALI, GEO_CODE, IN_CITY_LIMIT, COUNTRY_CODE, PHONE, ESTENSJONI, FAX, LAST_EXP_CHK_DTTM, FREIGHT_VENDOR,
                      INTERLINK_DLL, TMS_EXCLUDE_FLG
                 (nolock)
                FEJN
                  (SETID <> "SHARE") u
                  (ibaxxu(CARRIER_ID) >= Inqas(@ MinID)) u
                  (ibaxxu(CARRIER_ID) <= Inqas(@ MaxId)) u
                  (ibaxxu(Descr) SIMILI inqas(@ InputDescr))
                ]]>
            </Proprjetà>

I kien bil-kondizzjoni li SQL minn persuna DBA u jien mogħtija biex jifhmu li din hija speċjali view they created just for me. The unique key there is CARRIER_ID.

Hawn hu l-bug I introdotti:

      <Identifikaturi>
        <Identifika Isem="CARRIER_ID" TypeName="System.String" />
        <Identifika Isem="Descr" TypeName="System.String" /> 
      </Identifikaturi>

X'imkien matul il-linja, I kien irnexxielha jħawdu ruħi fuq it-tifsira ta ' <Identifikaturi> and added DESCR even though it’s not actually an identifier. I took DESCR out of the identifiers set and presto! Dan kollu ħadem.

I hope this saves someone some grief 🙂