People commonly ask about using a column of data type "Person or Group" in another column of data type "Calculated".

Боттом лине, ово не ради у ВСС 3.0 (или МОСС).

Када додајете израчунату колону, 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, То вам говори:

Један или више колона референце нису дозвољени, јер су колоне су дефинисане као тип података који није подржан у формулама.

Решење: 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.

Корисни линкови о обрачунатим поља у целини:

• Коришћење [Ме] у израчунатој колони
• Примери формула израза (љубазношћу http://jopx.blogspot.com/2007/10/calculated-fields-in-windows-sharepoint.html)

Брзо Дисцлаимер: Верујем горе да би било истинито и тачно, али сам видео довољно паметне трикове ту и тамо у Мосс / ВСС да не би било изузетно изненађен (Нестрпљиво ако хоћете) 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, молим вас јавите ми!

We did some heavy duty re-organizing of our site taxonomy via "Manage Content and Structure". For reasons unknown to me, this process (though working in the main) broke some navigation links in the quick launch. The broken links are characterized by:

• Wrong URL. На пример, it should be "/sites/departments/HumanResources/…". Међутим, the new link is "/sites/Corporate/HumanResources/…".
• Repeated bits on the query string of the heading, као у:

/sites/departments/HumanResources/_layouts/viewlsts.aspx?BaseType=0?BaseType=0?BaseType=0?BaseType=0

That’s easy enough to fix via site settings/navigation. Except, MOSS presents me with this when I try and do it:

The fact is, no one is making any change there (aside from me, наравно).

A quick search turns up this MSDN forums discussion: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1691577&SiteID=1

William Heurdier lays it out nicely in the the penultimate (као и од 10/02/07) после:

Fact is:

To reset corrupted headings, you have to :

– remove all the lists under corrupted heading

– remove corrupted heading

– From the list settings, add a removed list to the quick launch (This regenerate a non corrupted heading)

You are then good to go….

---

Sharepoint Expert – Sogeti Cap Gemini Switzerland

I was a bit confused because I kept wanting to go to the navigation page, make the change and then get hit with the "page was modified" message. Коначно, 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!

</крај>

Претплатите се на мој блог!

УПДАТЕ 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. Онда, sharepoint configuration utility on each server. Here is the MS Support link for that KB: http://support.microsoft.com/kb/932816.

Позадина:

Имамо пословну услов где еколошки инжењеринг менаџер треба да осигура да 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 (или њен помоћник) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Околина:

МОСС, 64 бит, виртуелна машина окружење (Развој кутија), 2 сервери (На СКЛ серверу #1, све остало на серверу #2).

Проблеми:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. Међутим, не ради добро из кутије (за нас).

1. Ток посао није требало да покрене, ever. I discovered this by reading through Кристофер Вајт (http://chrissyblanco.blogspot.com/2007/06/issues-with-delay-activity-in-moss.html) excellent write-up by using stsadm thusly:
   

   Ц:\>stsadm -o getproperty -propertyname "job-workflow" -УРЛ хттп://лоцалхост

   <Property Exist="No" />

   Ц:\>

   То је изненађујући резултат, али лако решити:

   Ц:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 минута између 0 и 59" -УРЛ хттп://лоцалхост

   Операција је успешно завршена.

   Ц:\>

   Када то раде, the first "In Progress" Ток брзо запали и урадио свој посао.

2. Нажалост, the next one didn’t work as expected. Срећом, Christopher refers us овде (http://support.microsoft.com/kb/932816). As of writing of this entry, чекамо ИТ одељењу да добије хитну исправку, but it does look promising. Our copies of the affected .dll’s do not share the same byte size, па се надам да ће решити проблем.

Решење:

Re-running the stsadm -o setproperty command seemed to prod the workflow timer awake. It would, грубо 7 минута касније, actually wake up and continue along with the workflow.

Питања / Питања којима се бави:

Пауза до датума не ради.

Пауза до датума не настави.

Workflow status does not change from "In Progress"

Workflow status stays "In Progress"