"Support for specifying 'L' and 'LW' with other days of the month is not implemented"
I was getting this error before when I WAS trying to specify some days of the month in addition to the last day, but now I am stumped as to why I am hitting this when I am only specifying "L" in the Day of Month portion of the cron expression. Any ideas would be appreciated.
From everything I have seen, if I want to do a REST based callout or schedule or abort a scheduled job programatically, there is no good way to bulkify that process. I realize that batch APEX could be used, but from what I have seen, there is no way to run system.schedule or system.abort using a list as an argument or run something like:
HttpRequest req = new HttpRequest();
req.setHeader('Authorization', 'Bearer ' + UserInfo.getSessionID());
req.setHeader('Content-Type', 'application/json');
req.setEndpoint(endpointUrl);
req.setMethod('GET');
Http h = new Http();
HttpResponse res = new HttpResponse();
try{
res = h.send(req);
}
catch(System.CalloutException e){
calloutError1 = e.getMessage();
}
using a list. So if I need to do something like this multiple times due to updates on multiple records, the best way I have seen to deal with it is to do the scheduled job or callout in a loop with an iterator that only allows a maximum number of iterations and then does exception handling if it goes over that number.
Am I missing anything here? Is there any way to bulkify these sorts of things or any best practices about this type of situation?
I am running in to an issue that I was hoping someone might have some insight in to. I have a method in a class triggered by contact insert or update. This method will check to see if a contact has a box checked and if it does, it will create a correspondinng user record with the ContactId set to the Id of the contact that was being created/edited.
The issue that I am having is with the test code coverage. I am getting the error "UNKNOWN_EXCEPTION, portal account owner must have a role". Now I have seen the workaround for this by creating a user with a role and then putting the community user creation code inside System.runAs context with the user you created. This works for community users created in the test class itself, however, if the test class is not actually creating the community user directly, but rather by creating a contact which triggers the class mentioned above to create a community user, it fails with the same role error mentioned above.
In all my searching, all I have found is a solution to the first issue where the community user is being created in the test class itself. I have not found any info for resolving it if the test class it then calling out to another class that creates the user. Any info on how I might be able to resolve would be greatly appreciated.
I am a bit stuck on a problem and I was hoping that someone might be able to help. I am creating an inline visualforce page with a page block table. the table displays different images on each row when a user clicks on the image but when the table refreshes, the rows in the table reorder themselves. the image changes correctly but I need the order of the rows to remain constant. I am really stuck as to trying to figure out why these rows are reordering themselves. any help would be greatly appriciated. the page and controller are below.
"Support for specifying 'L' and 'LW' with other days of the month is not implemented"
I was getting this error before when I WAS trying to specify some days of the month in addition to the last day, but now I am stumped as to why I am hitting this when I am only specifying "L" in the Day of Month portion of the cron expression. Any ideas would be appreciated.
From everything I have seen, if I want to do a REST based callout or schedule or abort a scheduled job programatically, there is no good way to bulkify that process. I realize that batch APEX could be used, but from what I have seen, there is no way to run system.schedule or system.abort using a list as an argument or run something like:
HttpRequest req = new HttpRequest();
req.setHeader('Authorization', 'Bearer ' + UserInfo.getSessionID());
req.setHeader('Content-Type', 'application/json');
req.setEndpoint(endpointUrl);
req.setMethod('GET');
Http h = new Http();
HttpResponse res = new HttpResponse();
try{
res = h.send(req);
}
catch(System.CalloutException e){
calloutError1 = e.getMessage();
}
using a list. So if I need to do something like this multiple times due to updates on multiple records, the best way I have seen to deal with it is to do the scheduled job or callout in a loop with an iterator that only allows a maximum number of iterations and then does exception handling if it goes over that number.
Am I missing anything here? Is there any way to bulkify these sorts of things or any best practices about this type of situation?
I am running in to an issue that I was hoping someone might have some insight in to. I have a method in a class triggered by contact insert or update. This method will check to see if a contact has a box checked and if it does, it will create a correspondinng user record with the ContactId set to the Id of the contact that was being created/edited.
The issue that I am having is with the test code coverage. I am getting the error "UNKNOWN_EXCEPTION, portal account owner must have a role". Now I have seen the workaround for this by creating a user with a role and then putting the community user creation code inside System.runAs context with the user you created. This works for community users created in the test class itself, however, if the test class is not actually creating the community user directly, but rather by creating a contact which triggers the class mentioned above to create a community user, it fails with the same role error mentioned above.
In all my searching, all I have found is a solution to the first issue where the community user is being created in the test class itself. I have not found any info for resolving it if the test class it then calling out to another class that creates the user. Any info on how I might be able to resolve would be greatly appreciated.
