• jhartfield
  • NEWBIE
  • 25 Points
  • Member since 2009

  • Chatter
    Feed
  • 1
    Best Answers
  • 1
    Likes Received
  • 0
    Likes Given
  • 8
    Questions
  • 14
    Replies

I was trying to update the code of our managed package. The Force IDE worked as usual, but after a refresh there were no changes on the code.

I tried to edit the Visualforce directly within the org and edited it by hand. After Saving without any errors I refreshed the code and there were also no changes!

 

Does anyone else have these problems since the rollback of the Spring 10 release?

 

Is there any tipp on how to save anyway?

 

I opened a case in the partner portal, but there are 4 Bugs with status new since the last 3 weeks without any reaction?!

Current documents has no example on how to schedule apex jobs every 10 mins. I tried with unix cron job syntax style (like 0,10,20,30,40,50 slots), that doesn't work.

 

Any help would be appreciated.

 

Thanks

 So what is the different? To illustrate my point, here are both way returning a similar set.

 

 #1

Set<String> nameSet = new Set<String>(); List<Account> acct = [SELECT Name FROM Account]; for(Account a_insert: acct){ nameSet.add(a_insert.Name); }

 

#2

Set<String> nameSet = new Set<String>(); for(Account acct : [SELECT Name FROM Account]){ nameSet.add(Name); }

 

Would I hit a limit earlier with #2 since I am storing the results in the sObject instead a list?




 

 

I randomly was trying a split today on a '*' field and got the following error:

 

System.StringException: Invalid regex: Dangling meta character '*' near index 0 * ^

 

Out of curiosity, I tried to split on '+' and got the same error.  

 

This is easily reproducible for me by running the following code in the execute anonymous window - can anyone else  confirm?

string sString = 'someStuff'; string[] splitted = sString.split('*');

 

 

Group and Professional Editions support Apex only in certified managed packages. If a certified managed package is installed into an org that doesn't otherwise support Apex, if that package contains an Apex class that implements the Schedulable interface, will we be able to schedule that class using the new scheduler?

I'm developing a VF page with a custom controller. I should be able to click the System Log link at the top of the page, see the System Log window appear, go back to my VF page, reload it, and then see a new Log appear in the System Log window, right?

 

The problem is that I don't see a new Log appear in the System Log window.

 

I've tried setting the Filter Settings to the lowest level possible (e.g., Finest), to no avail.  I've tried with the default Filter Settings. Nothing shows up in the "Logs recorded since..." list.

 

If I enter some Apex into the Execute Apex area and execute it, a log does show up in the list. But there doesn't seem to be anything I can do in my VF page that causes a log to be captured.

 

The only way I can get my VF page to display anything in the System Log window is if I turn on System / Monitoring / Debug Logs. But that's only good for 20 logs -- after that, I have to go back to System / Monitoring / Debug Logs and turn it back on again.  It's really unwieldy to have to do that when I'm trying to debug a VF page.

 

Before the new System Log feature, I could monitor what my VF page/controller was doing by just watching the System Log window. Now I have to repeatedly turn on Debug Logs -- is that really true? If so, is there any plan to correct that?

Message Edited by JeriMorris on 01-29-2010 12:48 PM

Hi All:  We have a managed app published on the AppExchange, and have recently created a new version where the only change made is that our Custom Tab uses the FULL WIDTH of the framed page versus the 2 column layout and the framed page length has been changed to 1300 pixels from 600.  We also changed the color of the tab.

 

I have confirmed these changes are inside the new package version we uploaded, and when I install the upgrade I see a notice that the Custom tab is the single component which will get upgraded....BUT...

 

PROBLEM:  Any SF instance which upgrades to our new version does NOT get the full width page, but instead gets the 2 column layout.   Interestingly, they do get the change to 1300 pixel page length from 600, but the change in the full width versus 2 column layout does NOT occur.  They also do not get the tab color change.

 

I'm going crazy with this!  Why can't we upgrade existing installs to switch from a 2 column layout to a full width layout??  Anyone have any insights?

 

Thanks in advance for any help!

 

Mark Cira @ PrintSf.com 

Message Edited by markcira on 01-04-2010 10:35 AM

Hi,

 

I have created some batch apex code alongwith other triggers and class/controller codes. 

 

When I run individual test methods on them, I am able to get test success result alongwith nice code coverage %. However when I run all tests together, I get following test failure errors:-

 

1)System.AsyncException: Database.executeBatch cannot be called from a batch or future method.

2)System.AsyncException: Future method cannot be called from a future method: changeOwners(String, String)

3)System.AsyncException: Future method cannot be called from a future method: getLead_Rollup_Amount(Id)

4)System.AsyncException: Future method cannot be called from a future method: changeOwners(String, String)

 

Please note again that the exceptions dont come when tested individually.

 

Please advise on same.

 

 

Thanks,

 

Vimal 

When I try to run all the unit tests via the 'Run All Tests' button found in Develop->Apex Classes, I have started getting the following message:

 

Maximum view state size limit (128K) exceeded. Actual viewstate size for this page was 150.625K

 

We have a pretty large ORG set up, so I'm sure it's because the system log has simply gotten too huge.  When we run all the unit tests by using the Eclipse IDE, the tests complete just fine, except we don't get a snapshot of the overall code coverage.  We just get code coverage on a class by class basis.

 

We want to be able to see where our overall code coverage is at.  Is there any other way to do this other than through the web interface?  Or, is there any way to make the unit tests less verbose through the web interface to reduce the size of the view state?