I am using metadata to deploy changes to my various environments. Since I have multiple BAs working in the same sandbox, they sometimes make field changes that do not need to be promoted to the other environments. In our package.xml, we are specifying every field in the CustomField section as opposed to doing a select all in the CustomObject. This provides a lot more granular control when we are merging to the different brances in our source control.

What I am noticing is that when i refresh my .object file, it is only grabbing the fields that are specified in my package.xml which I would expect. However, I notice that layouts seems to grab everything, including fields not specified in the package.xml. As you can imagine this causes issues because it now throws errors saying the CustomField does not exist.

Is this a defect in the metadata api? Or is there a workaround? Ideally i would not like to include some of these fields that potentially are POCs and not needed in Prod.

Looking to use Ping Identity as our IdP, and SFDC as the SP. For our use-case, we would like to pass additional attributes with the UserId, such as the Profile, with the request as another validation point for the IdP.

From all the documentation, it seems that we can only pass the UserId or the Federated UserId. Is this possible? If so, can you point me to the documentation or blog where i can do this?

Thanks!

I have created a Component that can lives on my Account, Contact, and Opportunity objects. WIthin the page i have a few outputPanels that allow for creation, editing, and list view of a Custom Object. On the List View, i have a link that will redirect the user to a different page.

When the Account object first loads my link is:
https://c.cs22.visual.force.com/apex/RelationshipListView

If i edit or create a new Custom Object, on the Save the URL will be:
https://vs.cs22.visual.force.com/apex/RelationshipListView

When i click the link with vs, as you would expect it gives me page not found error. Once i refresh my Account page though, the link will be correct, and route me to my intended page.

From what i have read, VFPs are hosted on a different domain, https://vs. rather than https://c.

Any ideas on how to fix this issue?

I have created a Component that can lives on my Account, Contact, and Opportunity objects. WIthin the page i have a few outputPanels that allow for creation, editing, and list view of a Custom Object. On the List View, i have a link that will redirect the user to a different page.

When the Account object first loads my link is:
https://c.cs22.visual.force.com/apex/RelationshipListView

If i edit or create a new Custom Object, on the Save the URL will be:
https://vs.cs22.visual.force.com/apex/RelationshipListView

When i click the link with vs, as you would expect it gives me page not found error. Once i refresh my Account page though, the link will be correct, and route me to my intended page.

From what i have read, VFPs are hosted on a different domain, https://vs. rather than https://c.

Any ideas on how to fix this issue?

I am using metadata to deploy changes to my various environments. Since I have multiple BAs working in the same sandbox, they sometimes make field changes that do not need to be promoted to the other environments. In our package.xml, we are specifying every field in the CustomField section as opposed to doing a select all in the CustomObject. This provides a lot more granular control when we are merging to the different brances in our source control.

What I am noticing is that when i refresh my .object file, it is only grabbing the fields that are specified in my package.xml which I would expect. However, I notice that layouts seems to grab everything, including fields not specified in the package.xml. As you can imagine this causes issues because it now throws errors saying the CustomField does not exist.

Is this a defect in the metadata api? Or is there a workaround? Ideally i would not like to include some of these fields that potentially are POCs and not needed in Prod.

I have created a Component that can lives on my Account, Contact, and Opportunity objects. WIthin the page i have a few outputPanels that allow for creation, editing, and list view of a Custom Object. On the List View, i have a link that will redirect the user to a different page.

When the Account object first loads my link is:
https://c.cs22.visual.force.com/apex/RelationshipListView

If i edit or create a new Custom Object, on the Save the URL will be:
https://vs.cs22.visual.force.com/apex/RelationshipListView

When i click the link with vs, as you would expect it gives me page not found error. Once i refresh my Account page though, the link will be correct, and route me to my intended page.

From what i have read, VFPs are hosted on a different domain, https://vs. rather than https://c.

Any ideas on how to fix this issue?