Granted this isn't Wonder. However, I can use my old patterns if EXExcelLook can't be integrated..
Anyway, what I wanted to was create a sort of custom reporting system. I need to find the values of individual to-one relationships based upon a qualifier of sorts.
Each project can have N number of metrics. So I thought I could just add a propertyKey... say... "primarySOW"
This is not in my EO per se, the value comes from say project.alignmentMetricForKey(String key); In other words, the key would be "primarySOW".
I wrote a custom component that would use the key to return the proper value.
Just trying to figure out how to wire it up.
Regards, James
On Dec 7, 2011, at 3:53 PM, David Holt wrote: What is this "failed" experiment?
The app will do whatever the rules do whatever you tell them to do. There's no magic.
How about giving us some information we can work with?
Rules? Stack trace? Anything??
What are you trying to do? If you have the list page, why can't you use it in ERExcelLook? Are you sure this will work without Wonder? Seems unlikely to an outside observer.
David
On 2011-12-07, at 1:42 PM, James Cicenia wrote: OK -
I was able to generate a standard D2wList. Still working the Excel part.
Anyway, my experiment proved wrong. I hoping the rules would intercept my "fake" property key and direct it to my custom component.
I didn't want to add these properties to the EO.
Do I have to?
James Cicenia
cell: 773.398.4649
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|