- General Development
- Schema Development
- Apex Code Development
- Visualforce Development
- Formulas & Validation Rules
- Force.com Sites & Site.com
- Chatter Development
- Java Development
- .NET Development
- Perl, PHP, Python & Ruby
- Desktop Integration
- APIs and Integrations
- Visual Workflow
- Apple, Mac and OS X
- VB and Office Development
- AppExchange Directory & Packaging
- Salesforce Labs & Open Source Projects
- Other Salesforce Applications
- Jobs Board
03-17-2010 05:09 AM
03-18-2010 01:33 PM
Can you please provide some more information about the tabs, objects and user permissions?
Are you using custom profiles in both cases? Custom v standard tabs? Which tabs and which permissions?
Not all tabs are supported (for instance, content is not an available tab). User permissions are also not supported in the metadata api.
03-23-2010 04:02 AM
Thanks for replying. Yes I am working with custom profiles with Salesforce Platform license.
About objects, I have seen mismatches in source and target profiles. For example standard
object Document has permissions mismatched. Same thing for other custom objects as well.
For custom tabs, I have seen mismatches for web tabs and VF page tabs.
Is there a documentation where I can find which portion of profile is supported by metadata api and which portion is not ?
Any more insights appreciated.
03-23-2010 08:56 AM
You can find the profile definition in the metadata api here .
The following is supported in some fashion:
What does your document object permission and vf tab code look like?
05-02-2012 11:52 AM
What ever happened here? We are seeing the exact same issues. It definitely seems to be isolated to Platform Licensing and the associated Profiles. The behavior is very odd. Tabs certainly change to "hidden". Object permissions randomly change. It's really frustrating.
I just checked the "Known Issues" page on the community site and this doesn't seem to be listed. We have submitted a case and will await a response.
05-02-2012 02:46 PM
Hi Kevino80 - We need more information to proceed. Can you please provide some XML Examples of where object permissions or tabs are configured but do not get set properly in the target org? Alternatively, can you share the case # for this issue so that I can look for the details I need from that case?
05-02-2012 04:50 PM
10-01-2012 07:27 AM
I am having similar issue here. We have few custom tabs, and when I export the profiles (using ant), the exported XML for one custom profile contains these tab visibilities (defaultOn, Hidden etc), where as another custom Profile has these tabs missing completely in the XML.
Is it dependent on any other setting for the profile?
01-30-2013 04:35 AM
The best way to do is, which is easy as well.
- Setup source project in Eclipse.
- Double click on profile, click on Source tab.
- Copy Source code and save in a file named profilename.profle
- If there are some component like field, tab object is missing from the destination org and you dont want to deploy them in the destination org, than remove it from the metadata and save only those component settings which you want to deploy.
- Deploy the metadata by ANT script.
04-18-2013 08:10 AM
Any updates on this issue? The workaround is very tedious when there are many profiles to deploy. We are also seeing this happen when deploying objects/profiles using the IDE for various clients.