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

ಬಾಟಮ್ ಲೈನ್, ಈ WSS ಕೆಲಸ ಮಾಡುವುದಿಲ್ಲ 3.0 (ಅಥವಾ MOSS).

ಒಂದು ಲೆಕ್ಕಾಚಾರ ಕಾಲಮ್ ಸೇರಿಸುವಾಗ, 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)

ತ್ವರಿತ ಹಕ್ಕು ನಿರಾಕರಣೆ: ನಾನು ಮೇಲೆ ನಿಜವಾದ ಮತ್ತು ನಿಖರ ಎಂದು ನಂಬುತ್ತಾರೆ, ಆದರೆ ನಾನು ಬಹಳ ಆಶ್ಚರ್ಯ ಎಂದು MOSS / WSS ಇಲ್ಲಿ ಮತ್ತು ಅಲ್ಲಿ ಸಾಕಷ್ಟು ಬುದ್ಧಿವಂತ ತಂತ್ರಗಳನ್ನು ನೋಡಿದ (ಆತುರದಿಂದ ನೀವು ತಿನ್ನುವೆ ವೇಳೆ) 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, ಈ ಪ್ರಕ್ರಿಯೆ (ಮುಖ್ಯ ಕೆಲಸ ಆದರೂ) 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.

ಹಿನ್ನೆಲೆ:

We have a business requirement where an environmental engineering manager needs to ensure that 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 (or her assistant) enters all the required permits and reminder dates at the start of the year. The system then does all the heavy lifting.

Environment:

MOSS, 64 ಸ್ವಲ್ಪ, virtual machine environment (development box), 2 servers (SQL on server #1, everything else on server #2).

Problems:

The Pause Until Date action seems like the perfect solution and it may well prove itself to be. ಹೇಗಾದರೂ, it does not work well out of the box (for us).

1. The workflow job was not scheduled to run, ever. I discovered this by reading through Christopher White’s (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" -URL HTTP://localhost

   <Property Exist="No" />

   ಸಿ:\>

   That was a surprising result but easily solved:

   ಸಿ:\>stsadm -o setproperty -propertyname "job-worfklow" -propertyvalue "every 1 ನಡುವೆ ನಿಮಿಷಗಳ 0 ಮತ್ತು 59" -URL HTTP://localhost

   Operation completed successfully.

   ಸಿ:\>

   Upon doing that, the first "In Progress" workflow quickly fired up and did it’s job.

2. ಶೋಚನೀಯವಾಗಿ, the next one didn’t work as expected. Thankfully, Christopher refers us ಇಲ್ಲಿ (http://support.microsoft.com/kb/932816). As of writing of this entry, ನಾವು hotfix ಪಡೆಯಲು IT ಇಲಾಖೆಗೆ ನಿರೀಕ್ಷಿಸುತ್ತಿವೆ, 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"