Template with LOOP.xxx error when used from a batch-job

Posted by smartsysISV on 29-Jun-2016 15:51

In a object I have a template wich uses

{!#LOOP_BEGIN.RXXXXXXXXX#3csOfiruQIyoL8zfP5ZHWg} - or - {!#LOOP_BEGIN.R245688140#RXXXXXX}

This template is used in a document template.

When my user is generating this doc-template this is ok, but if i use batchjobs to send this template as an email attachment, the lines is not ok

If I use only related fields without a view this is ok.

{!#LOOP_BEGIN.RXXXXXX}

I think the problem is that we can't give the system permission to views?

How can i fix this????????

Posted by smartsysISV on 18-Nov-2016 03:06

The Server API-role cannot be given permission on views.

This is reported an I have got the following answer in supportlink:

The behavior you had reported was expected in the past.

New enhancements are being built such that it would be possible to configure View permissions, and for Exchange Rates in the near-future release.

With that you will be able to overcome this issue.

All Replies

Posted by mpiscoso@gmail.com on 15-Nov-2016 19:11

What are the contents of your loop? are you referring to a report template btw?

For permissions I suggest you check the Server API role. Admin Setup > Roles > Server API if it is available in the public cloud. From there I often enable all create,edit, and view options for the role to minimize batch job issues.

Hope this helps.

Posted by smartsysISV on 18-Nov-2016 03:06

The Server API-role cannot be given permission on views.

This is reported an I have got the following answer in supportlink:

The behavior you had reported was expected in the past.

New enhancements are being built such that it would be possible to configure View permissions, and for Exchange Rates in the near-future release.

With that you will be able to overcome this issue.

Posted by mpiscoso@gmail.com on 18-Nov-2016 04:10

Sorry for the confusion, i didn't mean permission for views (which dont exist) but for the objects themselves.

Glad to hear that the view permissions are soon to be added.

You might still want to try enabling server api object permissions to minimize access issues in the future.

Hope that makes sense :)

This thread is closed