Hivyo, asubuhi hii, mwana wangu ni nia ya kuona umri-kumi na tatu ya vikwazo Halo 3 video katika Da. I’m outside shoveling snow, so I’m not there to help or hinder. Necessity is the mother of invention and all that … he has a eureka! moment. He realizes that even though Gamespot wants him to enter his halisi tarehe ya kuzaliwa, yeye kweli anaweza kuingia yoyote birth date he wants. Once he realized that, alijifanya kuwa na umri wa kutosha kuona video.
I’m not quite sure how I feel about this 🙂
Katika kazi yangu ya kwanza nje ya chuo katika 1991, Nilikuwa na bahati ya kufanya kazi kwa kampuni ya viwanda na 13 maeneo, not including its corporate HQ in New Jersey. I joined just when the company was rolling out a new ERP system. We were a small IT department of about ten people altogether, two of whom Did Not Travel. Part of the project involved replacing IBM System 36 boxes with HP hardware and HPUX. Everyone used green tubes to access the system.
mradi Rolls pamoja na mimi nina teremshiwa Baltimore na mpya ushirikiano mfanyakazi, Jeff. Our job was to power up the Unix box, kuhakikisha O / S alikuwa akikimbia, kufunga mfumo ERP, configure ERP, train people on the ERP and do custom work for folks on the spot. (Hii ilikuwa ni kazi ya ndoto, hasa kuja moja kwa moja nje ya chuo). Before we could really get off the ground, sisi zinahitajika kinafafanua zilizopo yote mabichi, put them on desks and wire them. And the best part was that we had to put the RJ11 connectors on ourselves.
Kwa sababu baadhi ya kuwa mimi kamwe kuelewa na kwa kweli kamwe mawazo ya kuuliza kuhusu wakati, sisi alikuwa alikuwa na baadhi ya kampuni ya kuambukizwa kuja pamoja na kukimbia cable katika kupanda, but we didn’t have them put on the connectors. Hivyo, there was a "patch box" with dozens of of unlabeled cables in the "computer room" na hizi snaked kuzunguka jengo kwa maeneo mbalimbali katika jengo.
Sisi kazi njia yetu kwa njia hiyo katika kipindi cha mwishoni mwa wiki, kupima kila waya, kuweka kwenye kontakt (maamuzi ya uhakika ni moja kwa moja vs. walivuka), kuhakikisha mazingira kidogo juu zilizopo kijani na Printers yalikuwa sahihi, labeling wires, making sure that "getty" was running correctly for each port and probably a thousand other things that I’ve suppressed since then. It all came together quite nicely.
Lakini, there was one important cable that we couldn’t figure out. The plant in Baltimore had a relationship with a warehousing location in New Jersey. Some orders placed in Baltimore shipped out of that location. There were two wires that we had to connect to the HPUX box: a green tube and a printer. The green tube was easy, lakini printer imegeuka kuwa ndoto ya wiki tatu.
Kama huna kujua ni, au kuzimwa ni, kushughulika na zilizopo kijani na Printers kwa njia hii, there are various options that you deal with by setting various pins. 8-bit, 7-bit, parity (even/odd/none), probably others. If you get one of those settings wrong, bomba au printer bado inaonyesha mambo, lakini itakuwa taarifa gibberish, or it will be gibberish with a lot of recognizable stuff in between. Bila shaka, these pins are hard to see and have to be set by using a small flat-edge screw driver. And they are never standard.
Sisi kuanzisha ya kwanza ya simu nyingi haraka na guy NJ (marakaraka kompyuta hater ambao pengine laana yetu kwa siku hii). We got the green tube working pretty quickly, but we couldn’t get the printer to work. It kept "printing garbage". We would create a new RJ11 connector, switching between crossed and straight. We would delete the port and re-created in Unix. We went through the arduous task of having him explain to us the pin configuration on the printer, never really sure if he was doing it correctly.
It’s about time to go live, everything in Baltimore is humming, but we can’t get the cursed printer up in NJ to work! We’ve exhausted all possibilities except for driving back up to NJ to work on the printer in person. To avoid all that driving, we finally ask him to fax us what he’s getting when it’s "garbage", matumaini kwamba labda kutakuwa na baadhi ya kidokezo katika takataka kwamba kutuambia nini sisi ni kufanya vibaya.
Tulipofika faksi, we immediately knew what was wrong. Kuona, our method of testing whether we had configured a printer correctly was to issue an "lp" amri kama hii:
lp / nk / passwd
Kimsingi, we printed out the unix password file. It’s always present and out of the box, always just one page. You standard Unix password file looks something like this:
smith:*:100:100:8-74(ofisi):/nyumbani / smith:/Usr / bin / sh :*:200:0::/nyumbani / mgeni:/usr/bin/sh
We had been printing out the password file over and over again for several weeks and it was printing correctly. Hata hivyo, kwa mtumiaji wa mwisho, it was "printing garbage".
</mwisho>
Mteja wangu hivi karibuni imewekwa kifaa uchawi kutoka Mreteni kwamba inaonekana kubadilishwa Cisco yao ya zamani mtandao mzigo balancer (NLB). At about the same time, sisi imewekwa hotfix kushughulikia tatizo workflow.
siku moja au mbili baadaye, sisi niliona tatizo wakati sisi kupatikana pamoja mtoa huduma (SSP). We could get to it, but we would be challenged for a user ID and password many times on each page. This didn’t happen with the main portal app, nor central administration. Naturally, hatukujua ambayo ya mbili (Mreteni au hotfix) itakuwa suala, ingawa mimi kwa dhati watuhumiwa hotfix, kuhesabia tulikuwa si imewekwa ni haki kabisa.
It turned out that Juniper had some kind of compression setting. Moja ya robed takwimu over in the network group turned that setting off. That solved our problem.
This is not the first time that compression has been the root cause of a SharePoint problem for me. IIS compression adversely affected a 3rd party tool from the good people at The Dot Net Factory for IE 6 browsers (IE 7 browsers kazi bila shida).
Hivyo, add "compression" kwenye orodha ya hatari.
</mwisho>
Mikopo kwa: http://www.elfwood.com/art/s/h/sherry/death_colour.jpg.html
I started off my "blogging career" using Microsoft’s platform and it’s been good to me. It’s easy to post, there are good options and widgets for managing your "space", decent web storage and so forth.
Hata hivyo, I really just fell into the MS solution with almost no planning. That alone calls for me to evaluate where I am and where I’m going, in terms of a blogging platform. There are also two important limitations that bother me right now vis-à-vis Windows Live Spaces.
Kwanza, I can’t get very good statistics. There are stats but the detail is often truncated and not presented in a way that allows for any kind of analysis. There no sorting or export capability. I get many blog ideas based on the kind of information people find (or especially fail to find) when they search my blog. It’s very hard to use lives spaces for that.
Pili, there does not seem to be any mechanism to "monetize" a windows live space blog. Kwa kweli, in order to get rid of MS ads (from which I derive no benefit), I need to actually pay Microsoft. (At least, that’s how I understand it; I have been unable to get definitive answers to this and questions like it).
Now that I’ve got an established pattern and set of blogging habits, I want to evaluate other options. I’ve done some research and there are a lot of choices, but I’m curious as to what other people, particularly others in the SharePoint community (as bloggers or readers), like to use.
If this subject interests you and you have an opinion or are willing to share your experience, please leave a comment or email me directly.
Shukrani!
<mwisho />
Forum watumiaji mara kwa mara kuuliza: Kwa nini SharePoint Designer kuweka ???? katika barua pepe yangu badala ya thamani shamba?
Moja ya sababu hii hutokea ni kwa sababu ya kutofautiana na ambayo rejea ni null.
This can happen because you are trying to reference a field from the "current item" lakini mtumiaji kamwe aliingia thamani ndani ya uwanja kwamba fomu.
<mwisho />
Mazingira: Katika workflow SharePoint Designer, you need to determine if a date field is blank.
Tatizo: SPD does not provide a direct method for comparing dates to anything other than a date. You cannot create a condition like this: "If [Tarehe Shamba] equals blank".
Ufumbuzi: Convert the date to a string. Use string comparison to determine if the date is blank.
Screen shots:
The following screen shots show how to do this. In this scenario, shamba juu ya bidhaa, "Environmental Permits:First Permit Reminder Date", ni kuwasilishwa na moto workflow katika kukabiliana.
Maelezo:
Wakati mimi walijaribu hii, I was pleasantly surprised to learn that it works. I was worried that SharePoint Designer might disallow the string assignment (Kutofautiana:StringReminderDateDate) lakini haikuwa kuruhusu.
Mimi pia alikuwa na wasiwasi kwamba kuruhusu ni, thamani inaweza kuwa batili na ama kulipua WF katika Runtime au labda kuongeza joto duniani 1/2 shahada, lakini wale wasiwasi walikuwa unfounded.
</mwisho>
Leo, I was working with a client and describing how to modify the content query web part and display additional bits of information from a content type.
"First, you configure the CQWP to connect to its data sources, then you export it to your workstation, modify <CommonViewFields>, upload, remove the original and now it’s ‘primed’ to display those other columns. Ijayo, open up SharePoint designer, navigate to the site collection root and locate ItemStyle.xsl. Copy one of the templates as a useful starting point. Go back and modify the CQWP to make use of this new template. Hatimaye, modify the template to render your new fields! (Don’t forget to check it back in so that other users can see the results)."
It’s all quite clear to me (and most of us SharePoint developer types) what’s going on and how it’s quite nice, kweli, that the data retrieval aspects of the CQWP are so well-separate from the data presentation aspects. Lakini, it’s not so easy to explain, is it?
<mwisho />
Nje ya boksi, Moss’ Content Query Mtandao Sehemu ya (CQWP) maonyesho ya matokeo yake katika muundo wa orodha, similar to search results. It is also possible to display the results in a grid format (i.e. HTML meza format). Grid formats are better in some circumstances. I describe how to achieve that effect in this article.
I have worked with a client on an enterprise-wide MOSS rollout. We have designed their taxonomy such that projects are first class citizens in the hierarchy and have their own top level site. Project managers maintain a singleton list of project summary information, kama vile jina, bajeti, inatarajiwa kukamilika tarehe, remaining budget and other summary type fields. By "singleton" I mean a custom SharePoint list guaranteed to contain only one item. Simplistically, inaonekana kama hii:
mbinu ya kiufundi ni nyingi sawa kama ilivyoelezwa hapa (http://paulgalvin.spaces.live.com/blog/cns!1CC1EDB3DAA9B8AA!447.entry). The CQWP uses an XSL transform to emit HTML for the browser to render.
I always envision the result before diving into the XSL because XSL is a nightmare. Here’s my desired result:
HTML kama hii inazalisha kwamba matokeo:
<html> <mwili> <kituo cha> <meza mpaka= 1> <!-- Labels -> <tr Bgcolor= Blue> <td><ni Michezo= Nyeupe><b>Mradi Jina</b></ni></td> <td align= Haki><ni Michezo= Nyeupe><b>Kukamilisha Tarehe</b></ni></td> <td align= Haki><ni Michezo= Nyeupe><b>Bajeti ya</b></ni></td> <td align= Haki><ni Michezo= Nyeupe><b>Gharama halisi</b></ni></td> <td><ni Michezo= Nyeupe><b>Hali ya jumla ya</b></ni></td> </tr> <tr> <td>Re-waya chumba cha kompyuta.</td> <td align= Haki>02/01/08</td> <td align= Haki>22,500.00</td> <td align= Haki>19,000.00</td> <td>Katika Maendeleo</td> </tr> <tr> <td>Utoaji servrar kwa Upgrade SQL</td> <td align= Haki>04/01/08</td> <td align= Haki>7,500.00</td> <td align= Haki>0.00</td> <td>Planned</td> </tr> </meza> </kituo cha> </mwili> </html> |
Fuata hatua hizi ili kujenga gridi ya taifa:
I’m going to concentrate on number six. Numbers one through four are straight-forward and something that any CQWP user has already done. Number five has been well-documented by others including this exhaustive screen-shot laden article from MSDN hapa (http://msdn2.microsoft.com/en-us/library/bb897399.aspx) na blog Heather wa Solomoni hapa (http://www.heathersolomon.com/blog/articles/CustomItemStyle.aspx).
Kuanza na kutekeleza hatua moja kwa njia ya tano kama kwa nyaraka MSDN na makala Heather wa Solomoni.
Katika hatua hii, ve aliongeza CQWP yako ya ukurasa na una yako <CommonViewFields> kimeundwa kama ni muhimu.
Kufuatia hatua kawaida, Mimi kupata matokeo haya ya kati:
1. Kujenga aina ya maudhui, a templatized custom list for that content type and two sites. Here is the content type:
Hapa ni muundo wa tovuti:
2. Kuongeza CQWP baada ya kujenga mradi subsites yangu na orodha ya mradi Singleton muhtasari:
3. Kuongeza taarifa yote ya ziada nataka kupitia <CommonViewFields>:
<mali jina="CommonViewFields" aina="string">Project_x0020_Name;Project_x0020_Expenses;Project_x0020_Status;Project_x0020_Start_x0020_Date;Project_x0020_End_x0020_Date;Project_x0020_Budget</mali>
Kumbuka kuwa nilikuwa na kuweka mashamba yote mali kwa line moja au itakuwa si kazi (CQWP bila kuniambia kuwa hoja akarudi vitu hakuna).
4. Katika hatua hii, we’re ready to move beyond the MSDN article and flip on over to Heather Solomon’s article. Follow her steps starting near step #5 kujenga customized / unghosted version of ItemStyle.xsl. I follow Heather’s advice, juu kupitia hatua 11 na kupata matokeo haya ya kati:
4.1: Jina langu XSL template kama ifuatavyo:
<xsl:template jina = "Grid" mechi = "Row[@Style=’Grid’]" mode = "itemstyle">
Mimi pia kidogo kurekebisha yake alipendekeza <xsl:kwa-kila …> kwa kuongeza <br /> kumtambulisha kutoa orodha safi:
<xsl:kwa-kila kuchagua="@ *"> P:<xsl:thamani ya kuchagua="jina()" /><br/> </xsl:kwa-kila>
4.2: Mimi kurekebisha sehemu mtandao, kwenda kuonekana na kuchagua yangu "Grid" style:
Kuomba mabadiliko na hapa ni matokeo:
Tunaweza kuona kutoka juu kwamba mashamba tunataka (Mradi jina, gharama, hadhi, nk) are available for us to use when we emit the HTML. Not only that, but we see the names by which we must reference those columns in the XSL. Kwa mfano, sisi rejea Mradi Hali kama "Project_x005F_x0020_Name".
Katika hatua hii, sisi kuondoka blog Heather na kutoka mabega ya makubwa haya, Mimi kuongeza kidogo yangu kidogo.
NOTE: Wakati wa kufanya mabadiliko ya ContentQueryMain.xsl wote kama vile ItemStyle.xsl, haja ya kuangalia files kurejesha kabla ya kuona athari za mabadiliko yako.
Kwa ajili ya gridi ya maamuzi madhumuni, MOSS uses two different XSL files to produce the results we see from a CQWP. To generate the previous bit of output, we modified ItemStyle.xsl. MOSS actually uses another XSL file, ContentQueryMain.xsl to in conjunction with ItemStyle.xsl to generate its HTML. As its name implies, ContentQueryMain.xsl ni kuu "" XSL that controls the overall flow of translation. It iterates through all the found items and passes them one by one to templates in ItemStyle.xsl. We’ll modify ItemStyle.xsl to generate the open <meza> tag kabla kutotoa moshi safu ya kwanza ya data na kufunga <meza> tag after emitting the last row. To accomplish this, ContentQueryMain.xsl ni iliyopita kwa kupitisha vigezo mbili katika gridi ya taifa yetu "" template katika ItemStyle.xsl, "Mwisho mstari" and "current row". ItemStyle.xsl uses these to conditionally emit the necessary tags.
Kutumia mbinu Heather wa Solomoni, we locate ContentQueryMain.xsl. It is located in the same place as ItemStyle.xsl. This screen shot should help:
Tunahitaji kufanya marekebisho yafuatayo:
Machapisho template aitwaye "OuterTemplate.CallItemTemplate" kutambuliwa na kamba:
<xsl:template jina="OuterTemplate.CallItemTemplate">
Kuchukua nafasi ya template nzima kama ifuatavyo:
<xsl:template jina="OuterTemplate.CallItemTemplate"> <xsl:kuacha jina="CurPosition" /> <!-- Kuongeza LastRow "" parameter. Sisi tu kutumia wakati style bidhaa kupita katika ni "Grid". --> <xsl:kuacha jina="LastRow" /> <xsl:kuchagua> <xsl:wakati mtihani="@ Sinema = 'NewsRollUpItem'"> <xsl:kuomba templates- kuchagua="." mode="itemstyle"> <xsl:na-param jina="EditMode" kuchagua="$cbq_iseditmode" /> </xsl:kuomba templates-> </xsl:wakati> <xsl:wakati mtihani="@ Sinema = 'NewsBigItem'"> <xsl:kuomba templates- kuchagua="." mode="itemstyle"> <xsl:na-param jina="CurPos" kuchagua="$CurPosition" /> </xsl:kuomba templates-> </xsl:wakati> <xsl:wakati mtihani="@ Sinema = 'NewsCategoryItem'"> <xsl:kuomba templates- kuchagua="." mode="itemstyle"> <xsl:na-param jina="CurPos" kuchagua="$CurPosition" /> </xsl:kuomba templates-> </xsl:wakati> <!-- Kupita nafasi ya sasa na lastrow kwa template itemstyle.xsl Grid. ItemStyle.xsl kutumia kwamba emit wazi na kufunga <meza> tags. --> <xsl:wakati mtihani="@ Sinema = 'Grid'"> <xsl:kuomba templates- kuchagua="." mode="itemstyle"> <xsl:na-param jina="CurPos" kuchagua="$CurPosition" /> <xsl:na-param jina="Mwisho" kuchagua="$LastRow" /> </xsl:kuomba templates-> </xsl:wakati> <xsl:vinginevyo> <xsl:kuomba templates- kuchagua="." mode="itemstyle"> </xsl:kuomba templates-> </xsl:vinginevyo> </xsl:kuchagua> </xsl:template> |
maoni kuelezea madhumuni ya mabadiliko.
Bila shaka, OuterTemplate.CallItemTemplate "" is itself called from another template. Locate that template by searching for this text string:
<xsl:template jina="OuterTemplate.Body">
Kitabu kupitia maelekezo katika OuterTemplate.Body na kuingiza parameter LastRow kama ifuatavyo (umeonyesha kama maoni katika italics):
<xsl:wito-template jina="OuterTemplate.CallItemTemplate"> <xsl:na-param jina="CurPosition" kuchagua="$CurPosition" /> <!-- Ingiza parameter LastRow. --> <xsl:na-param jina="LastRow" kuchagua="$LastRow"/> </xsl:wito-template>
Baada ya huu, sisi hatimaye kuwa mambo kuweka vizuri ili ItemStyle.xsl yetu inaweza emit <meza> tags katika mahali sahihi na.
NOTE: Tena, kuangalia katika ItemStyle.xsl baada ya kufanya mabadiliko yoyote ili kuona athari ya mabadiliko hayo.
Tuna kazi mbili hapa:
Kwanza, karibu na juu ya ItemStyle.xsl, kuongeza mstari huu:
<!-- Baadhi ya jumbo Mumbo kwamba unatuwezesha kuonyesha U.S. sarafu. --> <xsl:decimal-format jina="wafanyakazi" tarakimu="D" /> <xsl:template jina="Default" mechi="*" mode="itemstyle">
Kumbuka kwamba mimi aliongeza ni moja kwa moja kabla ya <xsl:template jina = "Default" …> ufafanuzi.
Ijayo, go back to our Grid template. Replace the entire Grid template with the code below. It is thoroughly commented, lakini usisite kunitumia email au kuacha maoni kwenye blog yangu kama una maswali.
<xsl:template jina="Gridi ya taifa" mechi="Row[@ Sinema = 'Grid']" mode="itemstyle"> <!-- ContentMain.xsl hupita CurPos na wa mwisho. Sisi kutumia haya masharti emit wazi na kufunga <meza> tags. --> <xsl:kuacha jina="CurPos" /> <xsl:kuacha jina="Mwisho" /> <!-- vigezo zifuatazo unmodified kutoka ItemStyle.xsl kiwango --> <xsl:variable jina="SafeImageUrl"> <xsl:wito-template jina="OuterTemplate.GetSafeStaticUrl"> <xsl:na-param jina="UrlColumnName" kuchagua="'ImageUrl'"/> </xsl:wito-template> </xsl:variable> <xsl:variable jina="SafeLinkUrl"> <xsl:wito-template jina="OuterTemplate.GetSafeLink"> <xsl:na-param jina="UrlColumnName" kuchagua="'LinkUrl'"/> </xsl:wito-template> </xsl:variable> <xsl:variable jina="DisplayTitle"> <xsl:wito-template jina="OuterTemplate.GetTitle"> <xsl:na-param jina="Title" kuchagua="@ Title"/> <xsl:na-param jina="UrlColumnName" kuchagua="'LinkUrl'"/> </xsl:wito-template> </xsl:variable> <xsl:variable jina="LinkTarget"> <xsl:kama mtihani="@ OpenInNewWindow = 'kweli'" >_blank</xsl:kama> </xsl:variable> <!-- Hapa sisi define variable, "TableStart". Hii ina HTML . Kumbuka kwamba kama CurPos = 1, ni pamoja na HTML katika tag CDATA. Vinginevyo, itakuwa tupu. thamani ya tableStart ni emited ItemStyle kila wakati inaitwa kupitia . --> <xsl:variable jina="tableStart"> <xsl:kama mtihani="$CurPos = 1"> <![CDATA[ <meza mpaka = 1> <tr Bgcolor = "blue"> <td><font Michezo = "nyeupe"><b>Mradi Jina</b></ni></td> <td align = "haki"><font Michezo = "nyeupe"><b>Kukamilisha Tarehe</b></ni></td> <td align = "haki"><font Michezo = "nyeupe"><b>Bajeti ya</b></ni></td> <td align = "haki"><font Michezo = "nyeupe"><b>Gharama halisi</b></ni></td> <td><font Michezo = "nyeupe"><b>Hali ya jumla ya</b></ni></td> </tr> ]]> </xsl:kama> </xsl:variable> <!-- Mwingine variable, tableEnd tu amefafanua meza kufunga tag. Kama na tableStart, inazidi daima emited. Hii ni kwa nini thamani yake ni . --> <xsl:variable jina="tableEnd"> <xsl:kama mtihani="$CurPos = $ Mwisho"> <![CDATA[ </meza> ]]> </xsl:kama> </xsl:variable> <!-- Daima emit yaliyomo ya tableStart. Kama hii si mara ya kwanza , basi tunajua thamani yake . Lemaza pato kukimbia kwa sababu wakati tableStart kuwa si tupu, ni . Kama , itakuwa kuzalisha<meza>" badala ya "<meza>". --> <xsl:thamani ya kuchagua="$tableStart" Disable-pato-kukimbia="ndiyo"/> <tr> <!-- P:Project_x005F_x0020_Name :Project_x005F_x0020_End_x005F_x0020_Date :Project_x005F_x0020_Budget :Project_x005F_x0020_Expenses :Project_x005F_x0020_Status --> <td> <xsl:thamani ya kuchagua="@ Project_x005F_x0020_Name"/> </td> <td align="haki"> <xsl:thamani ya kuchagua="@ Project_x005F_x0020_End_x005F_x0020_Date"/> </td> <td align="haki"> <xsl:wito-template jina="formatCurrency"> <xsl:na-param jina="thamani" |
UPDATE (04/2008): Hii kubwa blog kuingia inaonyesha nzuri javascript makao mbinu ya tatizo hili: http://webborg.blogspot.com/2008/04/add-functions-and-events-to-sharepoint.html
UPDATE II: (04/2008): Kuingia hii blog inaonekana kuahidi pamoja: http://www.cleverworkarounds.com/2008/03/13/free-mosswss-2007-web-part-hide-controls-via-javascript/
Mara kadhaa kwa wiki, kama si kila siku, forum users describe a requirement that would normally be met via cascading drop-downs. Kwa mfano, I have mbili udhibiti kuacha chini:
As responsible UI providers, we want it to operate like this:
There is no out-of-the-box support for this feature. Kwa kweli, there is no OOB support for any kind of direct intra-form communication. This includes programmatically hiding/enabling/disabling fields in response to field changes elsewhere on the form.
The real objective of this article to to describe possible solutions and these are the options as I know them:
If anyone knows other and/or better options, please post a comment and I’ll update the body of this post.
<mwisho />
To filter for a query for the Yes/No check box entitled "PG Milestone", configure CQWP kama hii:
Hii ni mwingine mmoja wa wale dhahiri-mara moja-wewe-know-it lakini maswali ngumu-kwa-kupata-jibu-kwa: Jinsi ya kuchuja juu ya sanduku Ndiyo / Hapana hundi kutumia hoja maudhui ya mtandao sehemu.
kwanza tafuta matokeo I find using the search term "filter yes/no content query web part" ni nje gorofa vibaya, hivyo nimeona d kuweka hii up huko na kuona kama anaweza kuchukua nafasi ya matokeo yasiyo sahihi katika matokeo ya kawaida tafuta.
Ni rahisi kabisa: True values = "1" and false values do not equal "1" (pretty retro, kweli).
Katika mfano wa hapo juu, I created site column of type "Yes/No (checkbox)" named "PG Milestone". I added it to a doc library, uploaded nyaraka chache, kuweka thamani kwa wanandoa na majaribio yake.
<mwisho />
