Cartlanna míosúla: Samhain 2007

MOSS Insíonn Mise Is é mo Colún Ainm Cosaint I nó Úsáide … Ach Ní Tá sé

Suas chun dáta 12/04/07: Féach Microsoft seo kB (http://support.microsoft.com/kb/923589) le haghaidh faisnéise a bhaineann le.

Dáiríre, casadh sé amach go bhfuil sé, ach tricksy MOSS bhí a dhéanamh deacair é a.

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, ach tá an toradh deiridh seo:

  • He tries to add a site column called "Quantity" agus freagraí CAONAIGH: "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. Dá bhrí sin,, "Quantity" ní ainm forchoimeádta.
  • He tries to find an existing site column named "Quantity" in that site collection. He cannot find it.

Rinne mé roinnt taighde, and even some coding, céirithe fealsúnachta agus ar deireadh fuair go raibh colún ainmnithe Cainníocht, i ndáiríre, exist. It was in the "_Hidden" group. Hence, Ní raibh muid ábalta teacht air tríd an comhéadan úsáideora SharePoint.

Conas a fuair sé ann? I do not know, ach tá mé teoiric (nó mar a bheadh ​​mo bhean ghlaoch air, "blah blah blah"). Áit éigin feadh na líne, a teimpléad daichead fabulous was added and probably activated at a site in the site collection. It was then deactivated (nó ar an láithreán bhaint). The site column, áfach,, remained but in the "_Hidden" group. If someone knows better, cuir in iúl dom trí r-phost nó tríd an bpost i na tuairimí.

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) Abair go bhfuil an t-ainm colún áirithe nó nach bhfuil sé. 2) Más rud é nach bhfuil sé ar cosnamh, thaispeáint ar an láithreán, nó ar a laghad an ngrúpa, ina bhfuil an t-ainm colún in úsáid cheana féin.

</deireadh>

Sonraí OM Reatha Trí Liosta Chustaim (nó, Ach eile Sonraí OM Displayor [cosúil le YACC, ach éagsúla])

Sa lá atá inniu, 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."

D'fhéadfadh an colún i gceist a chruthú, scriosadh agus ath-cruthaíodh i dtimpeallacht eile, so I knew it wasn’t a reserved name. Mar sin féin, Mé nach bhféadfaí a fháil ach an colún in áit ar bith tríd an comhéadan úsáideora caighdeánach SharePoint ag aon suíomh sa bhailiúchán láithreán.

Phost mé go Fóraim MSDN anseo agus an indomitable Andrew Woodward Léirigh mé i dtreo na sonraí bunúsacha tsamhail réad.

Chuaigh mé go dtí CodePlex a fháil ar roinnt uirlisí a bheadh ​​cabhrú liom piaraí i na sonraí OM bunúsacha agus cabhrú liom a aimsiú ar an deacracht.

Rinne mé roinnt uirlisí agus bhí siad an-fionnuar agus suimiúil ach sa deireadh, the UI wasn’t good enough for my purpose. I’m not criticizing them by any means, ach go soiléir nach raibh an uirlis-lucht bhfuil mo fhadhb i gcuimhne nuair a chruthaigh siad a n-UI :). Most people seem to be investing a fair amount of time and effort in creating workstation / iarratais cliant a chur ar fáil tuairimí crann, right-click context menus and so forth. These are nice and all, ach tá sé a lán oibre a chruthú taithí úsáideora barr-ar-an-líne go bhfuil freisin an-solúbtha.

Is gá mé i ndáiríre freagra ar an bhfadhb seo. Tharla sé domsa go má raibh mé in ann a fháil ar gach ceann de na colúin láithreán sa bhailiúchán láithreán i liosta saincheaptha, Raibh mé in ann a scagadh, shórtáil agus a chruthú tuairimí a bheadh ​​cabhrú liom teacht ar an colún supposedly atá ann cheana féin (rud a rinne sé, BTW). I went ahead and did that and an hour or two later, Bhí gach mo colúin láithreán luchtaithe isteach i liosta saincheaptha le grúpáil, sorting and so forth. I found my answer five minutes later.

Má bhíonn agus nuair mé a ghlacadh go rathúil ar fud an domhain, I think I will decree that all SharePoint tools providers must seriously consider surfacing their object model data in a custom list. That way, Tá mé an chumhacht chun cuardach a dhéanamh ar bhealach ar bith is mian liom (srianta, ar ndóigh, le caighdeán gnéithe SharePoint).

SharePoint Dearthóir Sreabhadh oibre Gníomhaíochta an Chustaim — Breathnadóireacht About <Cineál Field Dearthóir Ceangail =”StringBuilder” … />

Just breathnú tapaidh go bhfuil difríocht an-tábhachtach idir an dá sainmhínithe:

<FieldBind Field = "InParam1" Cineál Dearthóir = "Teaghrán Tógálaí" Id = "2" Téacs = "paraiméadar Ionchur # 1" />

i gcomparáid le:

<FieldBind Field = "InParam1" Id = "2" Téacs = "paraiméadar Ionchur # 1" />

Léiríonn an chéad mar seo i SPD:

íomhá

cé go léiríonn an dara ceann mar seo:

íomhá

Níl mé cinnte cé chomh cabhrach is atá na seatanna scáileáin seo ach rinne mé iarracht iad a dhéanamh ionas go mbeidh ort breathnú orthu 🙂

Is é an tuairim seo: StringBuilder is féidir leat a thógáil ar shraith (ar ndóigh) ag meascadh le chéile literals téad agus sonraí sreabhadh oibre (tríd an Add "Lookup" cnaipe sa chúinne íochtarach ar chlé). When you use the Add Lookup button, cuireann sé ina chomhartha san fhoirm "[%% chomhartha]". When SharePoint invokes your custom action, (C # cód i mo chás), SharePoint Gabhann an chomhartha féin, not the value of the token. If you use the default designer type (an dara cineál), SharePoint leathnaíonn an chomhartha agus Gabhann luach iarbhír an chomhartha ar do ghníomhaíocht.

StringBuilder = bad, Cineál dearthóir réamhshocraithe = MAITH.

Ar ndóigh,, 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 (atá teagmhasach go díreach cad a dhéanann duine a chruthú faoi réir dinimiciúil don ghníomhaíocht r-phost, ach tá go ábhar le haghaidh iontráil eile blog, Tá).

<deireadh />

Roimh Am Gníomhachtaithe Sreabhadh oibre — A Réiteach Neamh-leighis

Suas chun dáta: Féach ar an díospóireacht seo MSDN, go háirithe an iontráil seo caite: http://forums.microsoft.com/MSDN/showpost.aspx?postid=2631057&siteid=1. It describes a condition that may short circuit this whole thing. I mbeagán focal, d'fhéadfadh sé a bheith chomh simplí a dhéanamh ar a laghad ceann amháin de na réimsí éigeantacha.

Tá mé leabharlann doiciméad a thacaíonn le ocht cineálacha ábhar.

I have a SharePoint Designer workflow that wants to calculate and assign a "reminder date" ag simplí a dhealú 30 lá ó cholún eile, "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." (Is féidir leat níos mó eolas faoi chineál seo de KPI agus a léamh níos substaintiúla druil-síos anseo).

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.

Ní dhéanann an straitéis seo ag obair nuair a uaslódáil mé doiciméad.

I upload the document and I am presented with the meta data entry screen. Ag an bpointe seo, I’m already in trouble. SharePoint has already, ró-luath ó mo thaobhsa, fired the workflow. I haven’t had a chance to pick the correct content type nor assign a due date. Ag an am céanna, 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. Mar sin, … Tá mo sreabhadh oibre fired agus nuair a forghníomhaíodh é, 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, Roghnaigh mé an cineál inneachair ceart, enter the meta data and submit. The pause completes and the workflow proceeds as needed. (Tabhair faoi deara gur i mo thimpeallacht, timer workflow activities from SPD do not work out of the box. You may have the same trouble. Féach anseo le haghaidh tuilleadh sonraí).

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, ach tá mé nach bhfuil fós mhaith é.

Scríobh mé faoi seo ar na fóraim MSDN anseo: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2430725&SiteID=1

SharePoint Slándáil Bunúsaigh Chéad / Seachain Ceapa Tuisle Coiteann

Suas chun dáta 12/18/07: Féach alt Paul Liebrand do roinnt iarmhairtí teicniúla a bhaint de nó a mhodhnú ainm an ghrúpa réamhshocraithe (fheiceáil a comment thíos chomh maith).

Forbhreathnú:

SharePoint security is easy to configure and manage. Mar sin féin, 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. (Mé a admháil go bhfuil an fhadhb seo mé féin). This blog entry hopefully provides a useful SharePoint security primer and points towards some security configuration best practices.

Nóta Tábhachtach:

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 ríomhphost chugam. I’ll make corrections post haste.

Bunúsaigh:

Chun críocha an forbhreathnú seo, tá ceithre ghnéithe bunúsacha le slándáil: úsáideoirí / grúpaí, rudaí securable, leibhéil cead agus oidhreacht.

Úsáideoirí agus Grúpaí bhriseadh síos go dtí:

  • Úsáideoirí aonair: Ceirteacha tarraingthe ó eolaire gníomhach nó a cruthaíodh go díreach i SharePoint.
  • Grúpaí: 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" le rud securable leith.

Rudaí Securable bhriseadh síos go dtí ar a laghad,:

  • Láithreáin
  • Leabharlanna Doiciméad
  • Míreanna aonair i liostaí agus leabharlanna doiciméad
  • Fillteáin
  • Suímh éagsúla BDC.

Tá rudaí eile securable, ach gheobhaidh tú an pictiúr.

Leibhéil Cead: A carn de gráinneach / low level access rights that include such things as create/read/delete entries in lists.

Oidhreachta: 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.

Baineann úsáideoirí agus grúpaí chun rudaí securable trí leibhéil cead agus oidhreacht.

Na Rialacha Slándála chuid is mó tábhachtach a thuiscint, Riamh 🙂 :

  1. Tá Grúpaí simplí bailiúcháin na n-úsáideoirí.
  2. Tá Grúpaí domhanda laistigh de bhailiúchán láithreán (i.e. níl aon rud den sórt sin mar ghrúpa atá sainmhínithe ag leibhéal láithreán).
  3. Ainm grúpa d'ainneoin, Ní dhéanann grúpaí, i agus de féin, have any particular level of security.
  4. Groups have security in the context of a specific securable object.
  5. Is féidir leat leibhéil éagsúla cead a shannadh don ghrúpa céanna do gach réad securable.
  6. Polasaithe iarratas Gréasáin trump seo ar fad (Féach thíos).

Is féidir le riarthóirí Slándáil caillte i farraige de ghrúpa agus liostaí úsáideoirí brath i gcónaí ar na axioms a bhainistiú agus a thuiscint a n-chumraíocht slándála.

Ceapa Tuisle Coiteann:

  • Tuiscint ainmneacha Grúpa go bréagach cead: As an bosca, 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" Ní féidir le grúpa cur ar chor ar bith, ach amháin a léamh (mar shampla). This would not be a good idea, ar ndóigh, ós rud é go mbeadh sé an-mearbhall.
  • Ní shainmhínítear Grúpaí ag leibhéal láithreán. 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" nasc. 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.
  • Ní tuairiscíodh ballraíocht Grúpaí athrú ag láithreán (i.e. Tá sé mar an gcéanna i ngach áit go bhfuil an grúpa a úsáidtear): Consider the group "Owner" agus dhá shuíomh, "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, D'fhéadfadh liom rochtain a fháil ar na Daoine agus naisc Grúpaí tríd an láithreán AD, 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. Go deimhin, I’m removing her from the global Owners group. Hilarity ensues.
  • Má theipeann ar ghrúpaí atá bunaithe ar ról sonrach ainm: 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, Ba chóir dom a chruthaigh dhá ghrúpa nua: "HR Owners" and "Logistics Owners" agus leibhéil cead ciallmhar le haghaidh gach agus an méid íosta is gá do na húsáideoirí sin a gcuid oibre a shannadh.

Tagairtí Úsáideacha Eile:

Má tá tú rinne sé seo i bhfad:

Please let me know your thoughts via the comments or email me. If you know other good references, le do thoil a dhéanamh ar an céanna a!

Clibeanna Technorati:

Tapaidh agus éasca: Cruthaigh Sonraí View Gréasáin Cuid (DVWP)

Tá saibhreas eolais mór ar an SFP 3.0 Sonraí View Web Cuid (DVWP) on the web from several sources. Mar sin féin, 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" sraith chun aghaidh a thabhairt air.

Lean na céimeanna seo a chruthú mar chuid sonraí gréasáin dearcadh (DVWP). They are based on an "Announcements" chuid gréasáin, ach maidir le liostaí an chuid is mó.

  1. Cruthaigh chuid gréasáin Fógraí agus é a chur ar shuíomh.
  2. Oscail an suíomh i SharePoint Dearthóir.
  3. Oscail an tsuímh default.aspx.
  4. Select the Announcements web part and right-click.
  5. Ón roghchlár comhthéacs, select "Convert to XSAnT Data View".

SharePoint Dearthóir in iúl duit go bhfuil an suíomh seo saincheaptha anois óna sainmhíniú láithreán. Ní Sin gá go dona, ach tá impleachtaí tábhachtacha (feidhmíocht, uasghrádú, daoine eile) which are beyond the scope of this little "Quick and Easy" iontrála. To get more information on this subject, Molaim an dá leabhar anseo chomh maith le do cuardach idirlín is fearr leat.

Deimhnigh go ndearna tú é i gceart:

  1. Dún agus a ath-oscailt an brabhsálaí gréasáin (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" ón roghchlár.
  3. Osclaíonn an painéal uirlis chun an ceart.
  4. Tá an painéal athraithe óna roghanna atá leagtha gnách leis seo:
íomhá

“Ní féidir a fháil ar an scéimre liosta maoin colún ón liosta SharePoint” — Cur síos / obair-arounds

An tseachtain seo, atáirgeadh againn ar deireadh le fadhb a bhí thuairiscítear ag úsáideoir iargúlta: Nuair a rinne sí chun an t-ábhar ar liosta a onnmhairiú go dtí barr feabhais, bheadh ​​rudaí cosúil le tosú ag obair, ach ansin bheadh ​​Excel pop suas earráid: "Cannot get the list schema column property from the SharePoint list". She was running office 2003, windows XP and connecting to MOSS.

Chuardaigh mé an Internets agus chonaic roinnt tuairimíocht ach faic 100% definitive. Hence, an post seo.

An fhadhb: Onnmhairithe d'fhonn barr feabhais a tá a dháta (date = an cineál sonraí a an colún).

Cad a d'oibrigh linn: Convert the date to a "single line of text". Ansin,, é a thiontú ar ais go dtí dáta.

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

Tá an bug thrown scáth ollmhór thar an gcineál sonraí a dháta sa chliaint aigne, mar sin táimid ag dul a bheith ag lorg amach freagra deifnídeach ó Microsoft agus tá súil againn go mbainfidh mé sa phost agus a nuashonrú anseo sa tréimhse ghearr ama eile lena n-freagra oifigiúil agus eolas hotfix.

Tagairtí Eile:

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

<deireadh>

Liostáil le mo bhlag.

Clibeanna Technorati: ,

Quick agus Simplí: Seol ríomhphost le hyperlink leabaithe ó sreabhadh oibre Dearthóir SharePoint

Uair nó dhó sa mhí, post duine éigin ceist fóram: "Conas is féidir liom a áireamh hipearnasc le URL ná go bhfuil Inchliceáilte ó r-phost Dearthóir SharePoint?"

Á chur i láthair gan trácht breise: (go maith, iarbhír atá ann trácht a dhéanamh a thuilleadh tar éis an íomhá):

íomhá

Becky Isserman a leanas suas le míniú ar conas cabhrach a leabú nasc chuig mír sa ríomhphost: 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

Scaoileadh nua: Eisínteachtaí SharePoint Sreabhadh Oibre Dearthóir (feidhmeanna ionramháil teaghrán)

Suas chun dáta: Féach anseo le haghaidh mo smaointe ar thráchtálú an tionscadal seo: http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!569.entry

Bhí mé gnóthach ag obair ar mo tionscadal CodePlex atá dírithe faoi láthair ar sholáthar síntí ionramháil teaghrán chun sreabhadh oibre a cruthaíodh trí SharePoint Dearthóir.

Féach anseo le haghaidh sonraí:

Baile Tionscadail: http://www.codeplex.com/spdwfextensions

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

Leagan 1.0 Áirítear na gnéithe nua seo a leanas:

Feidhm Cur Síos (más rud é nach céanna. fheidhm Glan)
Num-iontrálacha() Returns the number "entries" in a string as per a specified delimiter.

Mar shampla: Num-entries in a string "a,b,c" with delimiter "," = 3.

Iontráil() Returns the nth token in a string as per a specified delimiter.
Fad String.Length
Ionadaigh() String.Replace()
Tá() String.Contains()
Returns the word "true" or the word "false".
Bhfotheaghrán(tús a chur) String.Substring(tús a chur)
Bhfotheaghrán(tús a chur,fhad) String.Substring(tús a chur,fhad)
Cos() String.ToUpper()
Ní eagar() String.ToLower()
StartsWith() String.StartsWith()
Returns the word "true" or the word "false".
EndsWith() String.EndsWith()
Returns the word "true" or the word "false".

A earráid runtime BDC Mhínigh

Ba chúis agam earráid BDC an tseachtain seo gur léiriú é féin ar an comhéadan úsáideora agus i 12 hive logáil ag runtime.

An Chéad, seo le feiceáil sa comhéadan úsáideora:

Níorbh fhéidir teacht ar réimsí a chur isteach gach Luachanna Aitheantóir a fhorghníomhú i gceart ar MethodInstance SpecificFinder leis Ainm … A chinntiú go bhfuil Paraiméadair ionchur TypeDescriptors a bhaineann le gach Aitheantóir sainithe don Aonán.

Seo lámhaigh scáileán:

gearrthóg_íomhá001

Raibh mé faoi deara freisin an teachtaireacht seo le feiceáil sa 12 logáil hive ag mbeidh (using my patented high-tech-don’t-try-this-at-home "Earráidí mistéireach" modh):

11/14/2007 09:24:41.27 w3wp.exe (0x080C) 0x0B8C SharePoint Portal Server Business Data 6q4x High Exception in BusinessDataWebPart.OnPreRender: System.InvalidOperationException: An luach Aitheantóir ”, Cineál ”, Is neamhbhailí. Expected Identifier value of Type ‘System.String’. ag Microsoft.Office.Server.ApplicationRegistry.MetadataModel.Entity.FindSpecific(Réad[] subIdentifierValues, LobSystemInstance lobSystemInstance) ag Microsoft.SharePoint.Portal.WebControls.BdcClientUtil.FindEntity(Eintiteas Aonán, Réad[] userValues, LobSystemInstance lobSystemInstance) ag Microsoft.SharePoint.Portal.WebControls.BusinessDataItemBuilder.GetEntityInstance(View desiredView) ag Microsoft.SharePoint.Portal.WebControls.BusinessDataDetailsWebPart.GetEntityInstance() ag Microsoft.SharePoint.Portal.WebControls.BusinessDataDetailsWebPart.SetDataSourceProperties()

Chuardaigh mé timpeall agus fuair roinnt mar thoradh ar an MSDN fóram, but they weren’t enough for me to understand what I was doing wrong. I watched a webcast by Ted Pattison go mo cuideachta Tá squirreled shiúl ar fhreastalaí agus tháinig a bhaint amach mo fhadhb.

I mo ADF, Tá mé ag nascadh le bunachar sonraí SQL mar a thaispeántar:

            <Maoin Ainm="RdbCommandText" Cineál="System.String">
              <![CDATA[
                ROGHNAIGH
                      , CARRIER_ID, EFFDT, DESCR, EFF_STATUS, TAXPAYER_ID, NETWORK_ID, FRT_FORWARD_FLG, ALT_NAME1, ALT_NAME2, LANGUAGE_CD,
                      TÍR, ADDRESS1, ADDRESS2, ADDRESS3, ADDRESS4, CATHRACH, NUM1, NUM2, HOUSE_TYPE, ADDR_FIELD1, ADDR_FIELD2, ADDR_FIELD3,
                      CONTAE, STÁIT, SEIRBHÍSÍ POIST, GEO_CODE, IN_CITY_LIMIT, COUNTRY_CODE, FÓN, EXTENSION, Facs, LAST_EXP_CHK_DTTM, FREIGHT_VENDOR,
                      INTERLINK_DLL, TMS_EXCLUDE_FLG
                 (nolock)
                ÁIT
                  (Leas <> 'SHARE') agus
                  (níos ísle(CARRIER_ID) >= Níos ísle(@ MinID)) agus
                  (níos ísle(CARRIER_ID) <= Níos ísle(@ MaxId)) agus
                  (níos ísle(DESCR) Mhaith níos ísle(@ InputDescr))
                ]]>
            </Maoin>

Cuireadh mé go SQL ó dhuine DBA agus tá mé thabhairt le tuiscint go bhfuil sé speisialta view they created just for me. The unique key there is CARRIER_ID.

Seo é an fabht thug mé:

      <Aitheantóirí>
        <Sainaithin Ainm="CARRIER_ID" TypeName="System.String" />
        <Sainaithin Ainm="DESCR" TypeName="System.String" /> 
</Aitheantóirí>

Áit éigin feadh na líne, Bhí éirigh liom a chur amú mé féin os cionn an bhrí <Aitheantóirí> and added DESCR even though it’s not actually an identifier. I took DESCR out of the identifiers set and presto! D'oibrigh sé go léir.

Tá súil agam go sábhálfaidh sé seo brón ar dhuine 🙂

Clibeanna Technorati: , , ,