Cartlanna míosúla: Nollaig 2007

Ag smaoineamh Maidir Táirgí Tráchtála

Chuir mé suas SharePoint tionscadal síntí Dearthóir suas ag CodePlex níos luaithe i mbliana agus cé tá sé i ndáiríre go leor teoranta ó thaobh raon feidhme, Measaim go bhfuil sé curtha íoslódáil ag 40 go 60 (b'fhéidir fiú 100) companies in just about two months. That indicates to me that there’s a market for that solution and if I were to successfully commercialize it, that could translate into a goodly amount of beer 🙂

Is é mo chúlra i ndáiríre i bhfad níos mó i bhforbairt an táirge agus tá a fhios agam cad atá ag teastáil a thabhairt táirgí barr-notch, i gcomparáid le tionscadal Caitheamh aimsire CodePlex, to market. In my saol atá caite, Bhí mé freagrach as táirge T&D for all software products. The difference between then and now is that I’m a consultant now working for an (den scoth) gnólacht dul i gcomhairle (Conchango). Roimhe seo, Bhí mé ag cuideachta ar fad taobh thiar dom agus i os comhair dom, selling and supporting the products we brought to market. Sa lá atá inniu, Ba mhaith liom a bheith ina n-aonar.

Tá mé smaointe a táirge éagsúla i gcuimhne, but I think the easiest would be to create a commercial version of the above-mentioned CodePlex project that uses that as a starting point and extends it further. My fuzzy off-the-cuff thinking is to charge something like $100 ar cheadúnas bhforbróir neamhtheoranta agus $500 per production web front end. I think I would also give away the source code.

Má tá smaointe nó taithí a bhfuil tú sásta a roinnt, fág nóta nó thoil ríomhphost chugam díreach. I’d like to hear opinions like:

  • An bhfuil sé fiúntach ar fad?
  • Moltaí praiticiúla do mhargaíocht, airgead a bhailiú, dháileadh.
  • Praghsáil.
  • Tacaíocht.
  • Aon tuairimí eile gur mhaith leat a fhágáil.

It’s "easy" chun teacht suas le smaointe a táirge agus iad a chur i bhfeidhm, though many dozens of hours of work are required. The other stuff is not as easy for me.

</deireadh>

Clibeanna Technorati:

Maidin Dé Domhnaigh greannmhar: “Jesus Must Die”

Cheannaigh muid ár gcéad (agus gan ach) "luxury" car back when hurricane Floyd nailed the east coast of the U.S. We got a LOT of rain here in New Jersey and roinnt laethanta a rith before life returned to normal. Just before Floyd struck, rinne muid tairiscint le haghaidh Volvo úsáid 850 GL agus tar éis Floyd bhuail, thiomáin sé abhaile.

It was our first car with a CD player. Like most new car owners, chuaigh muid ar CD dÚsachtach beag, revived our dormant CD collection and went on long drives just to listen to CD’s in the car. Like all fads, this passed for us and we ended listening to the same CD over and over again. I ár gcás, go raibh sé Íosa Críost Superstar.

Ceann de na (go leor) píosaí iontach sa mhéid is go ceoldráma carraig á chanadh ag na cineálacha foras crábhaidh, faoi ​​stiúir Caiaphas, the "High Priest". They sing their way into deciding how to handle the "Jesus problem" and Caiaphas directs them to the conclusion that "Jesus must die". The refrain on the song is "Just must die, Ní mór bás, Ní mór bás, this Jesus must die". You hear that refrain a lot in that piece.

Ag an am, my son was about three years old. You can probably see where this is going.

I came home from work one day and my son is in the living room playing with toys and humming to himself. I’m taking off my jacket, breathnú tríd an ríomhphost agus go léir mo siúlóid-an doras-i-is gnách stuif agus realize mé go tobann go bhfuil sé ag rá go díreach, Ní canadh i ndáiríre: "Jesus must die, Ní mór bás, must die." I was mortified. I could just see him doing that while on one of his baby play dates at a friend’s house — probably the last play date with that baby friend.

We pulled that CD out of the Volvo after that 🙂

</deireadh>

Clibeanna Technorati: ,

Google An raibh Glac Mo Beo Spásanna Blag Isteach an Clár AdSense

Suas chun dáta: Amhail an 03/09, I have found no way to integrate my live spaces account with Google Adsense. Microsoft’s system here seems to prevent all of the technical mechanisms that Google provides would-be adsense hosters. I tend to believe this is mainly a side effect of the security they’ve built into live spaces, not a direct effort to disable Adsense.

This is not a SharePoint post, but might be of interest to bloggers generally.

Someone commented on their Windows Live Spaces blog that Google affirmatively denied their application to participate in AdSense. She theorized that Google denied her because Windows Live Spaces hosts her blog. Mar sin féin, I was recently accepted into the program for my live spaces blog, so the policy has either changed or Google denied her for some other reason.

Ar ndóigh,, Ní féidir liom a fheiceáil aon bhealach soiléir a chomhtháthú Google AdSense i mo spás beo, but it’s a start 🙂

</deireadh>

Clibeanna Technorati: ,

Cur chun feidhme Máistir / Caidrimh Sonraigh Ag baint úsáide Liostaí Saincheaptha

Fóram úsáideoirí go minic mar ceisteanna mar seo:

> Dia duit,
>
> Do thoil, inis dom má tá aon féidearthachtaí a thógáil liosta saincheaptha le
> máistir agus sonraí cineáil (cosúil le sonraisc) gan úsáid a bhaint as InfoPath.
>

Soláthraíonn SharePoint roinnt amach as na gnéithe bosca a thacaíonn le cineálacha riachtanas gnó mar sin.

Go ginearálta, one links two lists together using a lookup column. List A contains the invoice header information and list B contains invoice details.

Bain úsáid as liostaí breise a choimeád ar bun líon na gcustaiméirí, uimhreacha a táirge, etc.

Bain úsáid as ábhar mar chuid gréasáin cheist (i CAONAIGH amháin) and/or a data view web part to create merged views of the lists. SQL Server Reporting Services (SRS) Tá fáil freisin ar an taobh tuairisciú air.

Mar sin féin, there are some important limitations that will make it difficult to use pure out-of-the-box features for anything that is even moderately complex. These include:

  • Méid na liostaí chuardaigh bhaineann vs. "smartness" of the lookup column type. A lookup column type presents itself on the UI differently depending on whether you’ve enabled multi-select or not. In either case, the out-of-the-box control shows all available items from the source list. If the source list has 1,000 míreanna, that’s going to be a problem. The lookup control does not page through those items. Ina áit sin, it pulls all of them into the control. That makes for a very awkward user interface both in terms of data entry and performance.
  • Lookups "pull back" one column of information. You can never pull back more than one column of information from the source list. Mar shampla, you cannot select a customer "12345" and display the number as well as the customer’s name and address at the same time. The lookup only shows the customer number and nothing else. This makes for an awkward and difficult user interface.
  • No intra-form communication. Tá mé scríofa faoi seo anseo. You can’t implement cascading drop-downs, coinníollach ar chumas / dhíchumasú réimsí, etc.
  • No cascading deletes or built-in referential integrity. SharePoint treats custom lists as independent entities and does not allow you to link them to each other in a traditional ERD sense. Mar shampla, SharePoint féidir leat a chruthú dhá liosta saincheaptha, "customer" and "invoice header". You can create an invoice header that links back to a customer in the customer list. Ansin,, you can delete the customer from the list. As an bosca, there is no way to prevent this. To solve this kind of problem, Ba mhaith leat é a úsáid de ghnáth láimhseálaithe imeacht.

Féadfaidh sé cosúil gruama, but I would still use SharePoint as a starting point for building this kind of functionality. Though there are gaps between what you need in a solution, SharePoint chuireann ar ár gcumas na bearnaí sin a uirlisí úsáid a bhaint as mar sin do líona:

  • Event handlers. Use them to enforce referential integrity.
  • Colúin saincheaptha: Create custom column types and use them in lieu of the default lookup column. Add paging, buffering agus gnéithe AJAX a dhéanamh sofhreagrach dóibh.
  • BDC. This MOSS-only feature enables us to query other SharePoint lists with a superior user interface to the usual lookup column. BDC can also reach out to a back end server application. Use BDC to avoid replication. Rather than replicating customer information from a back end ERP system, use BDC instead. BDC features provide a nice user interface to pull that information directly from the ERP system where it belongs and avoids the hassle of maintaining a replication solution.

    Is BDC gné CAONAIGH (nach bhfuil ar fáil i SSU) and is challenging to configure.

  • Bhfoirm gréasáin ASP.NET: Cruthaigh foirm AJAX-chumasaithe lán-feiceáil go n-úsáideann an tsamhail réad SharePoint agus / nó seirbhísí gréasáin do liostaí SharePoint ghiaráil am céanna ag soláthar comhéadan úsáideora an-sofhreagrach.

Féadfaidh an rogha dheireanach gur mhaith leat go bhfuil tú ag tosú ó scratch, ach smaoineamh ar an bhfíric go dtosaíonn an ardán SharePoint tú amach leis na gnéithe lárnacha seo a leanas:

  • Samhail Slándála, le cothabháil.
  • Córas Menu le cothabháil.
  • "Master table" (i.e. liostaí saincheaptha) le slándáil, tógtha-i cothabháil agus iniúchadh.
  • Cuardaigh.
  • Ar ais deireadh uirlisí comhtháthú (BDC).

Má tá tú tús le tionscadal nua folamh i stiúideo amhairc, bhfuil tú a lán de bhonneagar agus pluiméireachta a thógáil sula bhfaigheann tú gar do cad a thairgeann SharePoint.

I do believe that Microsoft intends to extend SharePoint in this direction of application development. It seems like a natural extension to the existing SharePoint base. Microsoft’s CRM application provides a great deal of extensibility of the types needed to support header/detail application development. Although those features are in CRM, the technology is obviously available to the SharePoint development team and I expect that it will make its way into the SharePoint product by end of 2008. If anyone has an knowledge or insight into this, fág tagairt le do thoil.

</deireadh>

Clibeanna Technorati:

Leid Thapa: Cuid Web Content Iarratas, Lookup Luach Colún agus XSL

I have a column name in a content type named "Real Estate Location".

That column is of type "lookup".

Tá mé modhnaithe <CommonViewFields> agus ItemStyle.xsl a thaispeáint ar an gcolún.

A simplí <XSL:luach-ar roghnú =…> tuairisceáin ar ais luach inmheánach go n-áirítear sonraí seasamh ordinal, mar shampla:

1;#Miami

Chun a fháil ar an luach daonna-chairdiúil, úsáid a bhaint as XSL bhfotheaghrán-tar éis, mar a thaispeántar:

<XSL:value-of select="substring-after(@ Real_x005F_x0020_Estate_x005F_x0020_Location,'#')"></XSL:luach-ar>

Bain úsáid as an teicníc aon uair a bhfuil tú ag obair le luachanna lookup i transforms XSL agus is gá a fháil ar an luach daonna-chairdiúil.

<deireadh />

Clibeanna Technorati: , ,

SharePoint Beagle Nollaig eisiúint Up & Beo

Go leor de fhios agat seo cheana féin, ach an t-eagrán na Nollag de SharePoint Beagle Is beo.

Tá gach airteagal fiú a léamh i mo thuairim.

Ba mhaith liom a bump beag breise a thabhairt do airteagal mo chomhghleacaí (Natalya Voskrensenskya). She provides a screen-shot extravaganza while describing how she used custom lists, sreabhadh oibre, SharePoint Dearthóir, data views and other elements to implement a self-service training feature in MOSS. She describes techniques that can be applied in many different business scenarios. Check out a bhlag cé go bhfuil tú ag sé.

Ná déan dearmad a sheiceáil amach mo airteagal as well 🙂 I wrote about using MOSS to help an HR department manage open positions.

</deireadh>

CAONAIGH Insíonn Me “Rochtana Diúltaithe” a Cuir Tasc Sreabhadh Oibre, Ach An bhfuil mé really An bhfuil Rochtain

I’ve implemented a workflow using SharePoint Designer in a site which is mainly read-only to "NT_AUTHORITY\Authenticated Users" (i.e. gach duine). There is a forms library for an InfoPath form. There is an associated workflow tasks list as well so that when the workflow operates, Is féidir é a tascanna a shannadh do dhaoine.

Bhriseadh mé cead don leabharlann foirmeacha agus liosta tasc ionas gur féidir aon úsáideoir fíordheimhnithe foirmeacha a chruthú agus a gcuid tascanna a shanntar thabhairt cothrom le dáta.

I test with my low-privileges test account.

An féidir liom a líonadh amach agus a shábháil bhfoirm a mbeidh an leabharlann? –>

An féidir liom rochtain a fháil ar an tasc ó nasc r-phost? –>

An féidir liom a fheiceáil ar an nasc Edit tasc sreabhadh oibre –>

An féidir liom a cliceáil ar an nasc? –> NÍL … Cead diúltaithe.

Cén fáth ar féidir liom a fheiceáil ar an nasc in eagar go denies cead dom nuair a bhím ag cliceáil ar sé? That’s not how it’s supposed to work…

Téim tríd an chumraíocht slándála arís, very closely. I do it again. Measaim scriosadh an post seo because I obviously don’t know anything about security.

Mar fhocal scoir, I search the Internets. I find this highly unlikely MSDN forum thread: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1838253&SiteID=17

The posters appear to be suggesting that the simple act of exporting the workflow to a drive platter will fix a MOSS security issue? I can hardly believe I just typed that. I’m reminded of the South Park episode about the 9/11 conspiracy where Stan is asking our Preznit, "Really?" over and over again.

Mar sin,, nothing to lose, I fire up SPD, right-click on the workflow and save it to my c:\ drive. That would be the c:\ drive on my laptop. I’m looking over my shoulder the whole time so that no one will ask me, "why are you saving that workflow to your laptop?"

Incredibly, that solves my problem. I can edit the task.

Ainmniú leis seo seo a bheith ar an chuid is mó Bizarre de Workaround Sreabhadh Oibre 2007.

</deireadh>

Clibeanna Technorati:

SharePoint Dearthóir, Mír reatha “Ionchódaithe URL Absalóideach” agus HTTPS

We often want to send an email that includes a hyperlink to the item or document that triggered the workflow. We can use current item’s "Encoded Absolute URL" for this purpose. Mar sin féin, it always seems to use "http" for the URL protocol. If your site runs on HTTPS then it will not work for you.

íomhá

Chomh fada is a fhios agam, there is no out of the box solution to this problem. If you need to use HTTPS, tá tú aon rogha amach as an bhosca.

Chun a réiteach é, create a custom action that provides a string replace function to use in your workflow. Alternatively, a úsáid mar uirlis 3ú páirtí, mar shampla an pacáiste den scoth anseo: http://www.codeplex.com/spdwfextensions 🙂

</deireadh>

Clibeanna Technorati: ,

Tapaidh agus éasca: Socraigh Colún Ainm inmheánaigh den Colún tSuímh

Suas chun dáta: Jeremy Thake Tá blogged faoi seo agus chur ar bun roinnt cód le haghaidh iarratas consól go léiríonn ainmneacha inmheánacha.

I was trying to get a content query web part to display a due date from a task and because the screen label is "Due Date", Ghlac mé go raibh an t-ainm colún a úsáid i <CommonViewFields> is "Due_x0020_Date".

Mícheart!

The real column name in this case was "DueDate".

Conas a raibh a aimsiú liom é? I re-read Heather Iontráil bhlag Sholamón ar mhodhnú CQWP to show additional columns of data. She describes this process at step #13. Trust it. It’s correct. Ar a laghad, it was correct for me. I did not trust it at first for another column with a much longer name.

I say "Trust it" because I did not trust it and probably wasted near two hours butting my head up against a wall. After I resolved the "DueDate" ainm, Theastaigh uaim a réimse eile a chur le <CommonViewFields>. Using the Solomon technique, I was getting a column name like "XYZ_x0020_Project_x0020_Due_x00".

Shíl mé go féin, that’s clearly a truncated name. I went ahead and un-truncated it with no success. I finally used the seemingly truncated name and it worked.

Bónas tip: Nuair a bhí mé ag obair leis an CQWP, má chuir mé ainm inmheánach dona <CommonViewFields>, the CQWP would tell me that the query had returned no results. Ach, má chuir mé cineál sonraí chuig an t-ainm réimse, it would return a result. Adding the data type actually masked a problem since I was referencing a non-existent field. I could add it, ach nuair a rinne mé a chur ar taispeáint a luach, I would always get a blank.

Ní raibh an masc an earráid:

<CommonViewFields>Due_x0020_Date;</CommonViewfields>

Seo raibh masc an earráid:

<CommonViewFields>Due_x0020_Date,Datetime;</CommonViewfields>

</deireadh>

Beware Athruithe Breaking go ItemStyle.xsl

Bhí mé ag obair le ItemStyle.xsl a shaincheapadh ar an cuma ar Ábhar Gréasáin Iarratas Cuid agus an ceart faoi am lóin, I made a breaking change to the xsl. I didn’t realize it, but this had far reaching effects throughout the site collection. I went off to lunch and upon my return, noticed this message appearing in a bunch of places:

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.

I blamed the client (not realizing as yet that it was my fault at this point) but eventually noticed that visual studio intellisense was warning me that I had malformed XSL. I corrected it and everything started working.

Be darned careful when working with ItemStyle.xsl (and any of the global XSL files) — breaking them affects many artifacts in the site collection.

<deireadh />