People commonly ask about using a column of data type "Person or Group" sa ibang hanay ng mga data type "Kinalkula".

Ika-line, na ito ay hindi gumagana sa WSS 3.0 (o Moss).

Kapag pagdaragdag ng isang kinakalkula haligi, WSS shows the list of fields it allows you to use for the calculation. If you type in the name of a column that is not in its list, ito ay nagsasabi sa iyo:

Isa o higit pang mga haligi ng sanggunian ay hindi pinahihintulutan, dahil ang mga haligi ay tinukoy bilang isang uri ng data na ay hindi suportado sa formula.

Workaround: Use an event handler. The event handler fires when the user saves the item. It performs the update you would have wanted the calculated column to do for you.

Kapaki-pakinabang na mga link sa mga kinakalkula patlang sa pangkalahatan:

• Paggamit [Sa akin] sa isang kinakalkula na haligi
• Mga halimbawa ng mga expression ng formula (kagandahang-loob ng http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

Quick disclaimer: Naniniwala ako sa itaas upang maging totoo at wasto, ngunit nakita ko na sapat na matalino tricks dito at doon sa Moss / WSS na hindi ko lubos na nagulat (sabik na sabik kung kalooban mo) if someone has figured out a way to do this without resorting to code. If you’ve figured out clever work-around or know someone that did, mangyaring ipaalam sa akin!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, ang prosesong ito (kahit na nagtatrabaho sa pangunahing) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. Halimbawa, it should be "/sites/departments/HumanResources/…". Gayunman, the new link is "/sites/Corporate/HumanResources/…".
• Paulit-ulit na mga piraso sa query string ng heading, tulad ng sa:

/mga site / mga kagawaran / HumanResources / _layouts / viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, Moss ay nagpapakita sa akin na may ito kapag sinusubukan kong gawin at ito:

Ang katotohanan ay, walang paggawa ng anumang mga pagbabago doon (bukod sa akin, mangyari pa).

Ang isang mabilis na paghahanap lumiliko up ang diskusyong ito sa MSDN forums: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier lays ito mabuti sa ang una sa huli (bilang ng 10/02/07) ipaskil:

Katotohanan ay:

Upang i-reset corrupt heading, mayroon kang upang :

– alisin ang lahat ng mga listahan sa ilalim ng heading na napinsala

– alisin Nasira ang heading

– Mula sa listahan ng mga setting, add a removed list to the quick launch (Ito papagbaguhing-buhay ang isang hindi sira ang heading)

Ikaw ay pagkatapos ay handa na upang patakbuhin….

---

Sharepoint Expert – Cap Gemini Sogeti Switzerland

Ako ay isang bit nalilito dahil ako iningatan kinakapos upang pumunta sa pahina ng nabigasyon, make the change and then get hit with the "page was modified" message. Eventually, I realized I had to go to the list settings and remove/add it to quick launch. That did the trick. Happy times are here again!

</dulo>

Mag-subscribe sa aking blog!

I-UPDATE 12/10/07: Hotfix as described in MSDN KB929816 solved the problem for us mentioned below. Obtain the hotfix and then install on each server on the farm. Pagkatapos, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Likuran:

Mayroon kaming isang negosyo na kinakailangan sa kung saan ang isang kapaligiran manager engineering Kailangang matiyak na 30 some-odd manufacturing locations located throughout the United States needs to ensure that those plants file for their various state-mandated permits in a timely fashion. One approach we’ve investigated leverages the "Pause Until Date" activity available to us via SharePoint Designer worfklow. The engineering manager (o ang kanyang katulong) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Kapaligiran:

Lumot, 64 kaunti, virtual machine kapaligiran (pag-unlad box), 2 server (SQL sa server #1, lahat ng iba pa sa server #2).

Problema:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Gayunman, Hindi ito gumagana ng maayos sa labas ng kahon (sa amin).

1. Ang daloy ng trabaho sa trabaho ay hindi naka-iskedyul na tumakbo, ever. I discovered this by reading through Christopher White ni (http://chrissyblanco.blogspot.com/2007/06/issues-with-delay-activity-in-moss.html) excellent write-up by using stsadm thusly:
   

   C:\>stsadm -o getproperty -propertyname "job-workflow" -url http://localhost

   <Property Exist="No" />

   C:\>

   Iyon ay isang kamangha-mangha resulta ngunit madaling malulutas:

   C:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 minuto sa pagitan ng 0 at 59" -url http://localhost

   Ang operasyon ay matagumpay na nakumpleto.

   C:\>

   Sa paggawa na, the first "In Progress" workflow mabilis fired up at ginawa ito ng trabaho.

2. Sadly, the next one didn’t work as expected. Thankfully, Christopher refers us dito (http://support.microsoft.com/kb/932816). As of writing of this entry, kami ay naghihintay para sa IT department upang makuha na hotfix, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, kaya sana ito ay malutas ang problema.

Workaround:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, humigit-kumulang 7 minuto mamaya, actually wake up and continue along with the workflow.

Tanong / Isyu natugunan:

I-pause Hanggang sa Petsa ay hindi gumagana.

I-pause Hanggang sa Petsa ay hindi ipagpatuloy.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"