SPWeb.Groups Vs SPWeb.SiteGroups

By -
SPWeb.Groups returns collection of cross-site groups which has some permission on the site. So if you add group from a site without any permission on the site, then this group wont appear in SPWeb.Groups collection, but it will appear in SPWeb.SiteGroups collection.

Comments

Post a Comment

Popular posts from this blog

Email content to a document library (MOSS 2007)

By -
let's assume the following names to the listed servers: Domain Controller - DC12345 Exchange Server - ES12345 MOSS 2007 Server - SP12345 (SMTP Enabled) Domain - mydomain.com Do the following on the server DC12345: 1. Access AD and create an OU under the domain - mossmails 2. right click mossmails and click delegatecontrol and add the service account you used for AD 3. Click Next 4. Select "Create a Custom Task to Delegate". Next, Next 5. Grant Read, write and create child objects permisions 6. Access DNS (Administrative tools>DNS) 7.Add an MX record in DNS for MOSS Server (Open dnsmgmt, right click the mydomain.com and add a new MX (mail exchanger) record 8. Name the Host or child domain > sp12345 9. Fully qualified domain name > sp12345r.mydomain.com Do the following on the server SP12345: 1. Central Admin.Operations>Topology& Services> Incoming Email Settings>Click Yes to enable incoming mail and the s...
Read more

Power Apps - Restricting the Text Box only Whole Numbers

By Vinod Thachin -
Image
 We can restrict the a Text box to allow only number by making the Format TextFormat.Number as below.  But this will allow decimal Number. We can restrict the Text Box to allow only whole numbers by writing the formulae for the TextBox Onchange as below If(     DataCardValue1.Text <> "" And Value(DataCardValue1.Text) <> RoundDown(         Value(DataCardValue1.Text),         0     ),     Notify("Please enter number without decimals");     Reset(DataCardValue1) )
Read more

Features - "You are not authorized to view this page" - Error 403

By -
Features are the new way to add functionalities to WSS 3.0 or MOSS 2007. If you are working with features a lot there is good chance you occasionally get a "You are not authorized to view this page" - Error 403 - when you try to manage your features - either site or web scoped. To manage features in the user interface you navigate to ManageFeatures.aspx. This can be very frustrating and may have you scratching your head. The fix is actually simple. Chances are you manually added a new feature to the FEATURES directory and did not inherit the FEATURES permissions. The error is slightly misleading. You are most likely authorized to view the page but the account is not authorized to access one or more of the files contained inside of the new feature. The most common reason the new directory and files do not inherit the correct permissions is because you cut and pasted one or more of the files to the new location. Cutting and pasting will bring along it's permissions while co...
Read more