+ Start a Discussion
rangambrrangambr 

Namespace issue - winter 15?

Hi,

One of our clients full sandbox (cs11) upgraded to winter 15 recently and there seems to be a namespace issue since then.

We have a managed app installed in this org and whenever SOQL is executed on a object in this manage package now it complains that object lookup is not found ("No such column on entity" ) All worked fine till this weekend and it seems strange why it is not working now.

It will be great if someone could provide some help on this.

Many thanks.
Best Answer chosen by rangambr
John TanquaryJohn Tanquary
Salesforce has officially recognized this problem as a Winter '15 pre-release "Known Issue" on https://success.salesforce.com/ under the Winter '15 Category with two distinct listings: "Internal server error when upgrade a package on Winter 15 orgs if custom fields name is the same as the namespace" (https://success.salesforce.com/issues_view?id=a1p30000000T5etAAC) and "Internal server error when installing package in winter 15 orgs if the package has custom field named the same as the package namespace" (https://success.salesforce.com/issues_view?id=a1p30000000T5eoAAC). Unfortunately, neither of these "Known Issue" listings provide a workaround. So be sure to press the green "This Issue Affects me" button in the upper right corner of each Known Issue listing to let Salesforce know that you are affected and to receive notifications from Salesforce on the status of the bug.

All Answers

KevinPKevinP
In the past, something like this has occured with recordtypes or currency codes. What's the field in play here?
rangambrrangambr
Hi Kevin,
Field is a custom lookup to another custom object in the managed package. We are not sure this is related to namespace any more. We can't even install our application in a winter 15 pre release org at the moment. When we try to install in provides " Error Number: 1655635892-1812 (-1979843694) ".

Thanks.
KevinPKevinP
Yeah, that would lead me to think there’s a deeper issue going on. --  Kevin Poorman Sent with Airmail
rangambrrangambr
Hi

We managed to recreate this issue and it seems that if we have a field with the api name same as the namespace for the package its contained in, compiler is unable to recoginise the field !. So we get ("No such column on entity" ) when we run a soql. We are unable to install/upgrade this package as some of the unit tests and rollup summary fields referencing this field. Does anyone know a workaround for this without having to recreate a new package with a different namespace or creating a new field with a different api name?

Thanks. 
John TanquaryJohn Tanquary
Salesforce has officially recognized this problem as a Winter '15 pre-release "Known Issue" on https://success.salesforce.com/ under the Winter '15 Category with two distinct listings: "Internal server error when upgrade a package on Winter 15 orgs if custom fields name is the same as the namespace" (https://success.salesforce.com/issues_view?id=a1p30000000T5etAAC) and "Internal server error when installing package in winter 15 orgs if the package has custom field named the same as the package namespace" (https://success.salesforce.com/issues_view?id=a1p30000000T5eoAAC). Unfortunately, neither of these "Known Issue" listings provide a workaround. So be sure to press the green "This Issue Affects me" button in the upper right corner of each Known Issue listing to let Salesforce know that you are affected and to receive notifications from Salesforce on the status of the bug.
This was selected as the best answer
rangambrrangambr
We have tested this in the orgs where the e-fix is applied and seems to work without any issues. Many thanks for fixing this.