11

Today two of my colleagues - one working on a na12 org and one working on a na15 org - have found that the meta.xml files that the Eclipse Force IDE pulls back for classes and triggers are missing the package version dependency element "packageVersions". They believe it was working earlier this week after Summer '13 had been rolled out. This is for several managed packages that we and third parties have created, and the problem is with the additional non-packaged code that we add for specific customers.

Has anyone else experienced this? Is it an enhancement (related to "InstalledPackage"?) or is something broken? If the latter, is there a workaround?

Improve this question
10
  • InstalledPackage is used to perform install and uninstall operations, my gut feel is that it is not related to this new feature and that this is a bug. I am interested to know if it is causing any other effects though, for example when you look at your package does it still list the other referenced packages as a dependency?
    – Andrew Fawcett
    Jun 25, 2013 at 12:43
  • RE: The case I raised per my answer below. I just had a call from Salesforce support to say they are looking into it and are aware other customers have raised it. They will provide me an update tomorrow.
    – Andrew Fawcett
    Jun 25, 2013 at 16:01
  • Thanks Andrew. I'll post here if I get anything back from support too.
    – Keith C
    Jun 25, 2013 at 20:57
  • 1
    Fyi, last update (late yesterday) on our case "I have escalated your case to Backline support Team. They will contact you soon."
    – Keith C
    Jun 26, 2013 at 10:49
  • 1
    Latest salesforce comment: "We have recognised as an issue and have requested a priority 1 fix, I will provide you an update with a tentative release date as soon as I get it. Unfortunately since this is not an intentional change I will not be able to comment on the side effects of deploying. We are exploring alternatives and workarounds at the moment and will keep you updated on the same as well."
    – Keith C
    Jun 27, 2013 at 12:50

4 Answers 4

Reset to default
6

**** UPDATE: 4th July 2013, Issue Resovled? ****

I now see this in my metadata XML file!

<?xml version="1.0" encoding="UTF-8"?>
<ApexClass xmlns="http://soap.sforce.com/2006/04/metadata">
    <apiVersion>28.0</apiVersion>
    <packageVersions>
        <majorNumber>1</majorNumber>
        <minorNumber>0</minorNumber>
        <namespace>packagea</namespace>
    </packageVersions>
    <packageVersions>
        <majorNumber>1</majorNumber>
        <minorNumber>0</minorNumber>
        <namespace>packageb</namespace>
    </packageVersions>
    <status>Active</status>
</ApexClass>

Salesforce have listed the issue and fixed here.

One oddity still is that the Versions tab still shows this...

enter image description here

I'll feed this back on my case see if they can explain this.

Original Issue Observations

Yes there is definitely something wrong here.

I have two test managed packages installed and I created the following...

public with sharing class TestPackageMeta {

    private packageb__Sales_Invoice__c sinv;

    private packagea__WorkOrders__c wo;
}

This resulted in this, no references to the packages...

<?xml version="1.0" encoding="UTF-8"?>
<ApexClass xmlns="http://soap.sforce.com/2006/04/metadata">
    <apiVersion>28.0</apiVersion>
    <status>Active</status>
</ApexClass>

However the strange thing is this, one reference to package a, but not package b....

enter image description here

Yet reassuringly Show Dependencies showed this...

enter image description here

I also checked that the package dependencies have not been affected and thankfully not...

enter image description here

I've also raised a case on our Premier support contract to see if we can get some traction on this, case number 09403195.

Improve this answer
2

There is now a "Known Issues" posting which is the best place to go to find out the status on the fix:

https://success.salesforce.com/issues_view?id=a1p30000000SyD7AAK.

Improve this answer
2
  • Amazing, I've been going back and forth with support to get an answer on this. The support rep I've been working with had no knowledge of this. A case of the right hand not knowing what the left is doing. Thanks.
    – tlfu
    Jun 29, 2013 at 11:03
  • I'm not sure, but I suspect this was raised as result of the cases we created, there is no date on it to confirm though. I agree though, would have been easier to point us to this if it did already exist.
    – Andrew Fawcett
    Jul 4, 2013 at 8:20
1

I too have noticed this. Last week we started noticing it on na15, but not na14, but as of June 25, it is now occurring on na14 as well. I have opened a case with Salesforce for clarification on this. It sounds to me like our friends at Salesforce are rolling out some change to the meta-data API.

Improve this answer
0

This does seem to be an issue and are working towards a fix.

However if there is no dependencies it is working right as we had cleaned up unwanted package references.

Improve this answer
1
  • Hi Vivek, I assume you are a Salesforce employee? Yes it has been raised before on StackExchange that the dependency information was always being included regardless of there being any dependency, once this regression is cleared up, this will be a most welcome improvement! Thanks for the update. :)
    – Andrew Fawcett
    Jun 27, 2013 at 14:50

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .