Answered by:
Activity Feeds View Breaking Solution Import

Question
-
I'm working on exporting a managed solution from a dev environment into another, clean environment. However, the solution will not import, due to dependency violations with the "Contacts Being Followed", "Contacts I follow", "Leads Being Followed", and "Leads I follow" views. Depending on how I tinker with the solution, the error can range from
"There was an error calculating the dependency: Error in Saved Query with ID ..."
to
"A managed solution cannot overwrite the SavedQuery component with Id=3a282da1-5d90-e011-95ae-00155d9cfa03 which has an unmanaged base instance. The most likely scenario for this error is that an unmanaged solution has installed a new unmanaged SavedQuery component on the target system, and now a managed solution from the same publisher is trying to install that same SavedQuery component as managed. This will cause an invalid layering of solutions on the target system and is not allowed."
But in either case, the culprit is one of those views relating to activity feeds. The Lead and Contact and Campaign Activity are the only out of the box entities in this solution. How do I get rid of this dependency?
The source org is an on-premise install, so Activity Feeds were manually deployed via the marketplace download. I've tried to import the managed solution export into both online and on-premise orgs.
Thanks!
Edit: If I remove the 4 views above from the customization.xml file that the export produces, I can then successfully import the solution. The views are, or course, still in the target system after import, because they're system views that come with Activity Feeds. But I'm not comfortable with that being the real solution, since I know it's unsupported to modify the XML directly in solution export.
Blog: http://andrewbschultz.com @andrewbschultz
- Edited by Andrew B Schultz Monday, March 12, 2012 10:18 PM
Monday, March 12, 2012 9:45 PM
Answers
-
Do you have Activity Feeds enabled on your development environment? If so, I suggest unconfiguring all of your entities for feeds in that enviornment. Only have the entities configured for testing purposes, and then unconfigure before you do your export.
Thanks,
Brandon
- Proposed as answer by Ajithg-MSFT Thursday, April 12, 2012 11:07 PM
- Marked as answer by Andrew B Schultz Thursday, April 26, 2012 5:14 PM
Thursday, April 12, 2012 10:53 PM -
Hi
This article explains whats happenning. As brandon mentioned ,if you are developing, then you should unconfigure all the entities for Activity feeds and publish all, before you do the export.
Thanks
Ajith
Thanks AjithG - MSFT
- Proposed as answer by Ajithg-MSFT Thursday, April 12, 2012 11:07 PM
- Marked as answer by Andrew B Schultz Thursday, April 26, 2012 5:14 PM
Thursday, April 12, 2012 11:07 PM -
Andrew
I think you still have references as the screen is showing. You could fix it using the following approach.
1. Click the Link for the Contact(Form), Lead(Form) from this grid and look for the Form Libraries to see if you still have the reference to the File. If so remove it.
2. Publish Contact and Lead Forms
3. Export the Site map and remove the references to the Whats new wall nodes in the Site Map and import it. ( You can use solution to add SiteMap and export and import the solution)
4. Publish All
I think the main reason it happened is you exported and imported unmanaged solutions in this org after you configured activity feeds and thus resulted in these dependencies.
Thanks
Ajith
Thanks AjithG - MSFT
- Marked as answer by Andrew B Schultz Thursday, April 26, 2012 5:14 PM
Monday, April 23, 2012 6:04 PM
All replies
-
So I removed the views fromthe customizations.xml file of an export of the unmanaged solution, and imported that solution into a fresh org. Then, I exported that solution (call it solution 2) as an unmanaged solution, deleted the original unmanaged solution in the environment where I originally built the solution. Then I imported solution 2 into the original environment again. When I exported this solution, I could then import it into other orgs.
Blog: http://andrewbschultz.com @andrewbschultz
- Marked as answer by Andrew B Schultz Wednesday, March 14, 2012 10:02 PM
- Unmarked as answer by Andrew B Schultz Thursday, April 5, 2012 4:40 PM
Wednesday, March 14, 2012 10:01 PM -
Re-opening this. Even though I took the steps above and it worked, the error recurred after updating some solution components in the dev environment. When I exported from dev and went to import into the test environment again, the error about the saved views was back.
Has anyone seen this?
Blog: http://andrewbschultz.com @andrewbschultz
Thursday, April 5, 2012 4:43 PM -
Do you have Activity Feeds enabled on your development environment? If so, I suggest unconfiguring all of your entities for feeds in that enviornment. Only have the entities configured for testing purposes, and then unconfigure before you do your export.
Thanks,
Brandon
- Proposed as answer by Ajithg-MSFT Thursday, April 12, 2012 11:07 PM
- Marked as answer by Andrew B Schultz Thursday, April 26, 2012 5:14 PM
Thursday, April 12, 2012 10:53 PM -
Hi
This article explains whats happenning. As brandon mentioned ,if you are developing, then you should unconfigure all the entities for Activity feeds and publish all, before you do the export.
Thanks
Ajith
Thanks AjithG - MSFT
- Proposed as answer by Ajithg-MSFT Thursday, April 12, 2012 11:07 PM
- Marked as answer by Andrew B Schultz Thursday, April 26, 2012 5:14 PM
Thursday, April 12, 2012 11:07 PM -
Thanks guys. This certainly looks like the right answer. Except, when I go to
Settings-> System-> Activity Feeds Configuration ->
There are no entries there. However, I still cannot delete the ActivityFeeds solution. Following are the details from the error:
Blog: http://andrewbschultz.com @andrewbschultz
Friday, April 13, 2012 3:23 PM -
Did you publish all customizations after unconfiguring the entities?
-Brandon
Saturday, April 14, 2012 12:14 AM -
I actually never removed them; they weren't there when I went in to look at them. But I did publish all customizations, and the condition still persists.
Blog: http://andrewbschultz.com @andrewbschultz
Monday, April 16, 2012 1:27 PM -
Are you using multiple forms? When you click on the "Contact (form)" or "Lead (form)" link in the dependency dialog do you see the "record wall?"
-Brandon
Monday, April 23, 2012 5:53 PM -
Andrew
I think you still have references as the screen is showing. You could fix it using the following approach.
1. Click the Link for the Contact(Form), Lead(Form) from this grid and look for the Form Libraries to see if you still have the reference to the File. If so remove it.
2. Publish Contact and Lead Forms
3. Export the Site map and remove the references to the Whats new wall nodes in the Site Map and import it. ( You can use solution to add SiteMap and export and import the solution)
4. Publish All
I think the main reason it happened is you exported and imported unmanaged solutions in this org after you configured activity feeds and thus resulted in these dependencies.
Thanks
Ajith
Thanks AjithG - MSFT
- Marked as answer by Andrew B Schultz Thursday, April 26, 2012 5:14 PM
Monday, April 23, 2012 6:04 PM -
No, we don't have multiple forms, but that's a good thought.
Blog: http://andrewbschultz.com @andrewbschultz
Thursday, April 26, 2012 5:14 PM -
Thanks Ajith - you're right, we did import unmanaged solutions after importing activity feeds, as I described earlier in the post.
Blog: http://andrewbschultz.com @andrewbschultz
Thursday, April 26, 2012 5:15 PM