You need to sign in to do that
Don't have an account?
mmix
describeLayout? or alternative? big problem
Hi, I am porting a wizard from crappy looking s-controls to a set of apex pages and I have some problems.
I can't seem to find a way to call describeLayout() for an SObject (Case in this case). I actually need access to methods:
recordTypeMappings(field).picklistsForRecordType()
I need this so I can limit the two dependent picklists based on the current record type. The <apex:inputField> seems to completely ignore the record type and picklist dependency and just shows all picklist values and apex framework does not seem to have describeLayout() support (?!?!?)
The only thing I can get is a List<Schema.PicklistValue> from Case.mylist.getDescribe().getPicklistValues() but this is not limited in any way. And hardcoding is not an option because picklists should be expandable without having to resort to coding again.
I also cannot find a validFor property in Schema.PicklistValue that keeps a bitmap for dependencies between values of two dependent picklists.
How can I obtain these informations? This is a big problem.
Message Edited by mmix on 12-09-2008 03:01 AM
I can't seem to find a way to call describeLayout() for an SObject (Case in this case). I actually need access to methods:
recordTypeMappings(field).picklistsForRecordType()
I need this so I can limit the two dependent picklists based on the current record type. The <apex:inputField> seems to completely ignore the record type and picklist dependency and just shows all picklist values and apex framework does not seem to have describeLayout() support (?!?!?)
The only thing I can get is a List<Schema.PicklistValue> from Case.mylist.getDescribe().getPicklistValues() but this is not limited in any way. And hardcoding is not an option because picklists should be expandable without having to resort to coding again.
I also cannot find a validFor property in Schema.PicklistValue that keeps a bitmap for dependencies between values of two dependent picklists.
How can I obtain these informations? This is a big problem.
Message Edited by mmix on 12-09-2008 03:01 AM
Please vote to add support for this, to me it should be considered a bug / gaping feature gap that it doesn't have this fundamental input type.
Message Edited by JeremyKraybill on 12-11-2008 12:28 PM
I voted, but it appears they are not taking this into consideration for spring 09 so who knows when and if it will happen. I don't understand all this, what are we talking about here, SF developers' egos? Do they refuse to acknowledge they messed up here? Without covering 100% of s-controls/webservice functionality the apex/visual force is just a half-baked product spawned from a nice idea.
Message Edited by mmix on 12-12-2008 12:57 AM