i have 3 objects named Book my show,rate detail ,and Rate master where Rate master is parent of Rate detail and book my show with the look up relationship in rate master there is no fields all the feilds are in rate details i need to fetch all the records of rate detail in book my show through rate master ...PLZ help
 

i have 3 objects named Book my show,rate detail ,and Rate master where Rate master is parent of Rate detail and book my show with the look up relationship in rate master there is no fields all the feilds are in rate details i need to fetch all the records of rate detail in book my show through rate master ...PLZ help
 

Hi all,

I would like to transfer my SF project on git - more specifically on Bitbucket. I would like to use tool for CI as well.
questions:
1. which tool is better to use - jenkins or bamboo? do both have an option to use it in the cloud, or do i have to install it locally?
2. how do i manage that one branch pushes changes to test enviornment and other one to do production?
3. is it a problem that multiple developers use same sandbox (that is the situation on our project, there is 3 of us)?

Any info is valuable, thank you in advance

Hi everyone,

We're attempting to get a path to production, utilizing CI as we don't have the time or budget to manually transition and merge changes from multiple developer groups up through the environments in our path to prod. We're looking at using git, ant, and jenkins (or similar). There are a lot of tutorials for how to implement that part, however I'm not really finding anything about how to manage package.xml when you have multiple developer groups pushing changes and need to merge the changes into a a chunk to have pushed to the next stage (while ensuring there is no loss of work). 

What's the best way to manage package.xml?

More in depth details below:

 

Our situation is that we're going to have multiple scrum teams performing config and code tasks (it's looking like each team will be around 70% config/30% code). They will each have a group sandbox. When they've finished a story, they will push the changes to git, which will in turn attempt to push the changes to a Dev Integration environment (to ensure each teams changes works with the others).

This will happen multiple times before all those changes will be need to be gathered and pushed to the QA environment (and then up to staging, and then to prod).

There are two goals that we need to accomplish that we are having trouble figuring out;

1) If team 1 changes an object, commits it, then team 2 does a commit without changing said object, it looks like it's possible team 2 could end up overwriting the work team 1 did (if they merge everything into the dev int branch). We need to ensure this doesn't happen.

2) Since there will be numerous commits from the various teams into DevInt before the collective changes get pushed to QA, we need a way to merge all of the changes since the last (good) push into one package.xml so that only what's been changed will be pushed out.

It looks like we may need to auto-generate the package.xml file on each commit/merge (in each branch) to include only what's actually been changed to handle these goals (unless there is a better way, or we're over-engineering here). 

Is this accurate? How would we go about auto-generating package.xml (I've found very few resources floating about the web)? Is this the best way to handle things in our scenario?

To make matters worse, we don't have a large budget for this (for example, I was looking at Flosum, but quickly got told we don't have the budget for it).

 

Thanks for any help anyone can give!

Hi All,

We have a situation to deploy client organization complete metadata (Like Packages, Objects, Classes, Sites etc..) to free developer edition since client org licences are going to expire and they are not ready to renewal those licences. But in future they might need these org, so we are trying to deploy the all components to DE. We have considered following options.

1. CloudAlly, a third party tool, we can take a backup of org(metadata and data) but we can't restore to another org.
2. Force.com IDE, we can take a backup of org(metadata but not installed packages), we need to re install all installed packages in developer edition (we have some paid packages so customer is not ready to pay again for these packages).

Please suggest the best ways to do this :)

Best Regards,
Mithun.

We have five developers working on integrating a Salesforce installation with a custom app we've built. We're using Canvas for a number of things, including a custom quoting tool. Each developer has a Developer Edition account, and our org has one production and one sandbox instance. Prod/Sandbox are being configured by an administrator who is adding custom objects, fields, and relationships that are needed for our org's sales process.

Unable to keep up with the pace of schema (metadata) changes happening on the Production/Sandbox environments, the five developers have had to abandon their Developer Edition accounts and use the Sandbox as a shared development environment. Part of the integration involves keeping data in sync between the database that our custom application uses, and the database our SFDC account uses. The problem we have now is that five developers share an SFDC dataset, but have different local datasets for the custom application data. We need to reference data in SFDC in the database for our custom application, so naturally, we constantly run into issues where the references to SFDC data only exist in the local DB of one developer, causing problems for the other four.

One solution would be to share a database for the custom application's data as well. This would be less than ideal, since as it's a development environment, the data is often erased and regenerated. Any need by one developer to do this would cause issues for four others.

I mentioned we use Canvas for a number of integrations. Currently, to enable development, we configure the canvas app to point at https://localhost. This means the five developers are the only ones who can view or demo the integrations. We could change it to point at our custom application's staging environment, but that would mean the developers would have to deploy every minor change to the custom application to staging in order to test them.

I can't imagine we're the first organization to run into these issues. How do others deal with them?