Quantcast
Channel: SCN : Popular Discussions - SAP BusinessObjects Design Studio
Viewing all 1411 articles
Browse latest View live

Message "Failed to create Java Virtual Machine" after starting Design Studio 1.2 SP1

$
0
0

Hi experts,

 

after I installed the SP1 of Design Studio 1.2 I become the Message "Failed to create java virtual machine" and I´m not able to start the Design Studio.

 

failed to create java virtual machine.png

 

My java version is 1.7

 

java_version.png

 

My SapDesignStudio.ini File (C:\Program Files\SAP BusinessObjects\Design Studio) looks like as follow:

 

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20130521-0416
-name
SAP
BusinessObjects
Design
Studio
-vmargs
-Xmx1024m
-Xms256m
-XX:PermSize=32m
-XX:MaxPermSize=512m
-XX:+HeapDumpOnOutOfMemoryError
-Dfile.encoding=UTF-8
-Dosgi.requiredJavaVersion=1.6
-Djava.net.preferIPv4Stack=true
-Djdk.xml.entityExpansionLimit=0
-Djavax.net.ssl.trustStoreProvider=SunMSCAPI
-Djavax.net.ssl.trustStoreType=Windows-ROOT
-Dorg.osgi.framework.os.name=win32

Any ideas or experiences?

 

Many thanks and regards,

Michael


Mandatory Bex variables Design Studio 1.2

$
0
0

Hi,

 

I'm a bit confused. According to this thread it is not possible to have mandatory Bex variables in DS.

It seems to work for my qry though, but the design is not what I would expect from it and is confusing for the end user. I was wondering how I can set the prompt as a popup like specified in this tutorial and also change the look and feel of it in order to make it more understandable for the end user.

 

Cheers

 

Eddy

Filter not working as expected. bringing all data sets

$
0
0

Hi,

 

I'm in Design Studio 1.2. My dashboard has multiple categories and each category is represented by a Button in the Dahboard. When I click on a category, it displays the corresponding result set in a graph and a table.

 

When there is no data for a particular category in a month, I would expect my graph and table to show no values, when I click on that category. But now it shows me all the records in graph and table. The filter for some reason is not working and that brings all the records into the graph and table.

 

When there is data it works fine. It shows the corresponding data for selected category.


Is anyone has faced this issue?

 

My dashboard is based on universe.

 

Regards

Saubhagya

DS SDK : Expand hierarchy in visualization

$
0
0

Hello,

 

I'm working my way through some D3 visualizations and have managed to get a tree diagram working thanks to this example:

 

http://www.d3noob.org/2014/01/tree-diagrams-in-d3js_11.html

 

The visualization takes a dimension object with an activated hierarchy and renders it like this:

 

DS_Tree.png

With a crosstab component I can get the tree to expand:

 

DS_Tree_CT.png

 

Now I want to extend this to function like the Collapsible Tree from Mike Bostock:

 

http://bl.ocks.org/mbostock/4339083

 

I've incorporated the transitions from the update function, which all work well, but the problem comes with the click event, which is handled in the D3 code with this function:

 

// Toggle children on click.
functionclick(d) {
  if (d.children) {
  d._children = d.children;
  d.children = null;
  } else {
  d.children = d._children;
  d._children = null;
  }
  update(d);

 

This is called in the update function when the nodes are declared:

 

        // Declare the nodes

        var node = svg.selectAll("g.node")

        .data(nodes)

        .enter().append("g")

        .attr("class", "node")

        .attr("transform", function(d) { return "translate(" + d.y + "," + d.x + ")"; })

        .on("click", click);

 

I can see the event being fired, and d._children being switched with d.children, but nothing happens in my visualization. I even tried modifying the function to set the metadata property nodeState, hoping this would alter the datasource, but to no avail:

 

            function click(d) {

            if (d.children) {

              d._children = d.children;

              d.children = null;

              if (d.nodeState)

              {d.nodeState = "EXPANDED";}

            } else {

              d.children = d._children;

              d._children = null;

              if (d.nodeState)

              {d.nodeState = "COLLAPSED";}

            }

            update(d);

          }

 

In the console, I can see the property d.nodeState change from EXPANDED to COLLAPSED when I set the appropriate break point, but nothing changes in the viz

 

I'm guessing I need to do something differently to interact with the data source and change it's state but I couldn't find anything in the guide. Unfortunately, the Simple Crosstab sample doesn't provide the expand/collapse functionality either, though it does render the plus signs that indicate a hierarchy node is available.

 

Any ideas on how I can add this interactivity to my extension would be very welcome.

 

Thanks,

Jim

Problem with Component or missing any settings

$
0
0

I have a Problem with my listBox OutPut Display in Design Studio 1.3:

 

Have Two Data source:

 

  1) DS_1 for Dimension Filter

 

  2) DS_2 for ListBox

 

 

Bex Query DS_1 has fields/columns like Country key and Country Name of Member Array Type

 

 

Another Bex Query DS_2 has fields/columns like Country key, Country Name(Member Array) , State Names(Member Array)

 

 

 

Now when i select single/multiple member items from an Country Dimension Filter, Iam trying to display the selected countries and each country with required Statenames in my listBox OutPut Display. For this i tried so far with the below lines of code in script of Dimension Filter which was not displaying as expected.

 

 

 

 

   var Countries = DS_1.getFilterText("YCoun");

        var aCountry = Countries.split(";");

               

                   aCountry.forEach(func(country, i){

                         

                    LISTBOX_1.addItem("" + i, country);

                     var aState=DS_2.getMembers("YStat", 10);

 

 

                       aState.forEach(func(state) {

 

 

                         LISTBOX_1.addItem(state.internalKey, state.text);

                          DS_2.setFilterExt("YCoun", Countries);});});

 

 

Tried searching the entire forum if for any two datasources settings needed in dimension filter and refering the documentation didnt get any clue so far.

 

 

Any ideas? is this default behaviour in Dimension Filter or am i missing something wrong on the code mentioned above.

 

 

Thanks so much

- Dinya.

Message "Failed to create Java Virtual Machine" after starting Design Studio 1.2 SP1

$
0
0

Hi experts,

 

after I installed the SP1 of Design Studio 1.2 I become the Message "Failed to create java virtual machine" and I´m not able to start the Design Studio.

 

failed to create java virtual machine.png

 

My java version is 1.7

 

java_version.png

 

My SapDesignStudio.ini File (C:\Program Files\SAP BusinessObjects\Design Studio) looks like as follow:

 

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20130521-0416
-name
SAP
BusinessObjects
Design
Studio
-vmargs
-Xmx1024m
-Xms256m
-XX:PermSize=32m
-XX:MaxPermSize=512m
-XX:+HeapDumpOnOutOfMemoryError
-Dfile.encoding=UTF-8
-Dosgi.requiredJavaVersion=1.6
-Djava.net.preferIPv4Stack=true
-Djdk.xml.entityExpansionLimit=0
-Djavax.net.ssl.trustStoreProvider=SunMSCAPI
-Djavax.net.ssl.trustStoreType=Windows-ROOT
-Dorg.osgi.framework.os.name=win32

Any ideas or experiences?

 

Many thanks and regards,

Michael

How to set Filter default display value as selected value

$
0
0

Hi All,

.

   I have three filters(Plant,material and year). i am getting the data on charts  based on filter default values

 

 

in plant filter on select i have given code bellow

 

DS_1.setFilter("Z_PPCD",PLANT.getSelectedValue());

 

MATERIAL.setItems(DS_1.getMemberList("Z_MATPCD", MemberPresentation.INTERNAL_KEY, MemberDisplay.TEXT, 50));

 

in material filter,

 

DS_1.setFilter("Z_MATPCD",MATERIAL.getSelectedValue());

 

YEAR.setItems(DS_1.getMemberList("0CALYEAR", MemberPresentation.INTERNAL_KEY, MemberDisplay.TEXT, 50));

 

in year filter,

 

DS_1.setFilter("0CALYEAR", YEAR.getSelectedValue());

 

 

 

when i run the report i am getting the all the data from data base

 

DSError.jpg

 

 

DSError1.jpg

Passing Parameters with OpenDocument in SAP Design Studio

$
0
0

Hello everybody,

 

I have built 2 Design Studio dashboards. One Design Studio dashboard should act as an overview, the other Design Studio dashboard should act as a more detailed view. The detailed view is based on a BEx Query, which contains several mandatory variables. Now I want to jump from the overview to the detailed view an pass the chosen parameters from the overview dashboard to the detailed dashboard by setting the mandatory query variable with an OpenDocument link. I know that this works fine with other BusinessObjects tools like Web Intelligence, but I was not able to set the mandatory BEx Query variables using OpenDocument in Desing Studio. Does anyone know if this works yet, or maybe in further releases?

 

Thank you in advanced.

 

Best regards

 

Stephan Bucher


Dynamic measure in charts using same data source

$
0
0

Hi Experts,

 

I am trying to use single data source to show chart for selective measures. I have tried the steps here: Design Studio 1.2: Select key figures to display on charts. Here we can create multiple charts with selective measures using single data source.

But, is it possible to re-use the same chart component ? I mean, selecting a measure name from a drop down, I want to change the measure in the same chart component - using one chart component and one data source. Is it possible using some script ?

 

I tried but could not find an option for a chart component to change the dimension/measure. I do not want to have one chart for each measure and show/hide based on the selection. I want a single chart and want to change the objects dynamically using some script.

 

Regards,

Arijit

Problem Initial View and others

$
0
0

Hi all,

 

recently we updated to DS 1.4 and our BW to 7.4 SP09.

Now we are facing some problems that did not arise before these updates but until now I am not able to exactly determine the reason and therefore I have no idea how to solve these.

 

Maybe one of you have any idea.

 

My first problem is the following:

 

In my application I have serveral datasources. For them you are normally able to select the displayed measures and keyfigures within the "initial view" tab.

Inside this tab it seems to work as normal but when closing it, the view in my application does not change.

It is like DS is not able to save the selected view but I don't understand why.

 

WDesign Studio I get this error message:

 

Could not bind a reference of component com.sap.ip.bi.base.application.DeclaredServiceActivator. The reference is: Reference[name = IActivatorBase, interface = com.sap.ip.bi.base.bundle.IActivatorBase, policy = dynamic, cardinality = 0..n, target = null, bind = addRICActivator, unbind = removeRICActivator]

 

I just looked in the path: C:\Program Files\SAP BusinessObjects\Design Studio\plugins

and there is no such "com.sap.ip.bi.base.application.DeclaredServiceActivator" - should there be one and this is the problem?

 

------------------------------------------------------------

---UPDATE----

I just created a totally new dashboard with only one new Datasource.

Now DesignStudio gives me no error message at all but I still cannot change the shown keyfigures in the initial view tab.

After closing the initial view selection, Design Studio will always show ALL keyfigures from the query in the crosstab.

When using this data source with a chart component, I am able to select the shown keyfigures in the chart poperties.

------------------------------------------------------------

 

 

In other dashboards I had a conversion routine in some queries and now DS is no longer able to load these.

Then I get following messages:

 

eclipse.buildId=@qualifier@

java.version=1.7.0_55

java.vendor=SAP AG

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE

Framework arguments:  BusinessObjects Design Studio

Command-line arguments:  -os win32 -ws win32 -arch x86_64 BusinessObjects Design Studio

 

Error

Mon Jan 12 11:04:21 CET 2015

ERROR [f65382e7-dff1-4a74-8f78-345dc1115107]: Termination message sent

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

ERROR

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

 

com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

ERROR

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:211)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageByListener(MessageManager.java:177)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:129)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:207)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageByListener(MessageManager.java:177)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:129)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:207)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageByListener(MessageManager.java:177)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:129)

    at com.sap.ip.bi.base.application.service.RfcService.fillMessages(RfcService.java:358)

    at com.sap.ip.bi.base.application.service.RfcService.doPostProcessing(RfcService.java:307)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.doPostProcessing(ProviderSelectionObject.java:1817)

    at com.sap.ip.bi.base.application.service.rfcproxy.base.RfcFunction.execute(RfcFunction.java:97)

    at com.sap.ip.bi.base.application.service.RfcService.doPostProcessing(RfcService.java:316)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.doPostProcessing(ProviderSelectionObject.java:1817)

    at com.sap.ip.bi.base.application.service.rfcproxy.base.RfcFunction.execute(RfcFunction.java:97)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderInfoObject.prepareForSelectionMemberAccess(ProviderInfoObject.java:1698)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderComponentList.setup(ProviderComponentList.java:145)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderComponentList.isSingleMemberSelection(ProviderComponentList.java:414)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.selection.ComponentList.isOnlySingleMembersSelection(ComponentList.java:1108)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Sorting.supportsSortBySelection(Sorting.java:457)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Sorting.getType(Sorting.java:208)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Sorting.setSortByMembersPresentation(Sorting.java:251)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSorting(StateDomParser.java:3243)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseQvSorting(StateDomParser.java:3122)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseQvCharacteristicNode(StateDomParser.java:2016)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseCharacteristic(StateDomParser.java:1645)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.CharacteristicList.setStateFromDom(CharacteristicList.java:92)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.readListObjectDetails(StateDomParser.java:4274)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelectorNode(StateDomParser.java:293)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseQueryViewNode(StateDomParser.java:368)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelectorNodeBase(StateDomParser.java:253)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelector(StateDomParser.java:212)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelector(StateDomParser.java:165)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.readStateFromDom(SelectionObject.java:1489)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.setDefaultStateByXml(SelectionObject.java:1627)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.initializeState(SelectionObject.java:718)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QueryView.initializeState(QueryView.java:182)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.initialization(SelectionObject.java:684)

    at com.sap.ip.bi.base.application.impl.ServiceManagement.registerService(ServiceManagement.java:776)

    at com.sap.ip.bi.base.application.impl.ServiceManagement.createService(ServiceManagement.java:397)

    at com.sap.ip.bi.base.application.impl.ServiceManagement.createService(ServiceManagement.java:365)

    at com.sap.ip.bi.base.application.impl.Application.createService(Application.java:491)

    at com.sap.ip.bi.base.application.service.base.BaseServiceDescription.createService(BaseServiceDescription.java:142)

    at com.sap.ip.bi.webapplications.dataproviders.selector.impl.WdpSelector.doInit(WdpSelector.java:325)

    at com.sap.ip.bi.webapplications.runtime.object.page.impl.PageObject.init(PageObject.java:296)

    at com.sap.ip.bi.webapplications.runtime.object.provider.impl.Provider.init(Provider.java:37)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.initPageObject(PageStateProcessor.java:2798)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.setupPageObject(PageStateProcessor.java:2104)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.createPageObject(PageStateProcessor.java:2061)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageCommandProcessor.doCreateDataProviderCommand(PageCommandProcessor.java:819)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.doCreateDataProviderCommand(Page.java:5933)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:606)

    at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:155)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:425)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:340)

    at com.sap.ip.bi.webapplications.runtime.processor.CommunicationProcessor.processCommand(CommunicationProcessor.java:212)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandSuper(Page.java:4910)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommand(Page.java:4476)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommand(Page.java:1)

    at com.sap.ip.bi.web.runtime.template.impl.items.TemplateAssembler.createPageObjects(TemplateAssembler.java:655)

    at com.sap.ip.bi.web.runtime.template.impl.xml.XmlTemplateAssembler.reloadTemplate(XmlTemplateAssembler.java:182)

    at com.sap.ip.bi.web.runtime.template.impl.xml.XmlTemplateAssembler.doInit(XmlTemplateAssembler.java:94)

    at com.sap.ip.bi.web.runtime.template.impl.items.TemplateAssembler.init(TemplateAssembler.java:162)

    at com.sap.ip.bi.webapplications.runtime.impl.object.template.Template.doInit(Template.java:144)

    at com.sap.ip.bi.webapplications.runtime.object.page.impl.PageObject.doInit(PageObject.java:344)

    at com.sap.ip.bi.webapplications.runtime.object.page.impl.PageObject.init(PageObject.java:296)

    at com.sap.ip.bi.webapplications.runtime.rendering.renderer.ItemRenderer.init(ItemRenderer.java:41)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.initPageObject(PageStateProcessor.java:2798)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.setupPageObject(PageStateProcessor.java:2104)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.createPageObject(PageStateProcessor.java:2061)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.setTemplate(Page.java:5440)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageCommandProcessor.doSetTemplateCommand(PageCommandProcessor.java:1698)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.doSetTemplateCommand(Page.java:6028)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:606)

    at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:155)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:443)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:340)

    at com.sap.ip.bi.webapplications.runtime.processor.CommunicationProcessor.processCommand(CommunicationProcessor.java:212)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandSuper(Page.java:4910)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandInternal(Page.java:4569)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandSequence(Page.java:4729)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.doProcessRequest(Page.java:2574)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page._processRequest(Page.java:780)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processRequest(Page.java:5157)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processRequest(Page.java:5150)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller.doProcessRequest(Controller.java:1244)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller._processRequest(Controller.java:1094)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller.processRequest(Controller.java:1060)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller.processRequest(Controller.java:1)

    at com.sap.ip.bi.server.runtime.sevice.impl.BIRuntimeServerService._handleRequest(BIRuntimeServerService.java:524)

    at com.sap.ip.bi.server.runtime.sevice.impl.BIRuntimeServerService.handleRequest(BIRuntimeServerService.java:907)

    at com.sap.ip.bi.server.execution.engine.runtime.LocalBIExecutionService.executeRequest(LocalBIExecutionService.java:47)

    at com.sap.ip.bi.client.execution.AbstractExecutionServlet.handleRequest(AbstractExecutionServlet.java:146)

    at com.sap.ip.bi.client.servlet.BIPrivateServlet.handleRequest(BIPrivateServlet.java:35)

    at com.sap.ip.bi.client.execution.AbstractExecutionServlet.doPost(AbstractExecutionServlet.java:125)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

    at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)

    at org.eclipse.equinox.http.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:38)

    at com.sap.ip.bi.zen.webserver.designer.ZenSessionFilter.doFilter(ZenSessionFilter.java:45)

    at org.eclipse.equinox.http.servlet.internal.FilterRegistration.doFilter(FilterRegistration.java:81)

    at org.eclipse.equinox.http.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:35)

    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:132)

    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

    at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:386)

    at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)

    at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)

    at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:229)

    at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)

    at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)

    at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)

    at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)

    at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)

    at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)

    at org.eclipse.jetty.server.Server.handle(Server.java:370)

    at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)

    at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:982)

    at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1043)

    at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)

    at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)

    at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)

    at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667)

    at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)

    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)

    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)

    at java.lang.Thread.run(Thread.java:812)

 

At the moment most of our dashboards don't work and I am desperately looking for a solution.

 

Regards

 

Steffen

Cross tab Scroll bar in Design Studio

$
0
0

Hi All,

 

I have inserted  multiple cross tab with data. In a particular tab i have hug data where i must use Horizontal scroll.   I wrote code in css , like

#CT_1.sapzencrosstab-HScrollTable {

  display: bold;

}

 

It is working fine. But that scroll bar is applying to all cross tabs in application. I needed to apply only for one table (CT_1).

 

Thanks & Regards,

Sud.

How to set Filter default display value as selected value

$
0
0

Hi All,

.

   I have three filters(Plant,material and year). i am getting the data on charts  based on filter default values

 

 

in plant filter on select i have given code bellow

 

DS_1.setFilter("Z_PPCD",PLANT.getSelectedValue());

 

MATERIAL.setItems(DS_1.getMemberList("Z_MATPCD", MemberPresentation.INTERNAL_KEY, MemberDisplay.TEXT, 50));

 

in material filter,

 

DS_1.setFilter("Z_MATPCD",MATERIAL.getSelectedValue());

 

YEAR.setItems(DS_1.getMemberList("0CALYEAR", MemberPresentation.INTERNAL_KEY, MemberDisplay.TEXT, 50));

 

in year filter,

 

DS_1.setFilter("0CALYEAR", YEAR.getSelectedValue());

 

 

 

when i run the report i am getting the all the data from data base

 

DSError.jpg

 

 

DSError1.jpg

Design Studio 1.2 SDK - including SAPUI5 libraries

$
0
0

Hi,

 

There will be times when it would be beneficial to include SAPUI5 controls within an SDK component, either on the canvas or the additional properties sheet.  In this context, I'd appreciate a clarification and any guidance regarding how to reference SAPUI5 libraries within the Design Studio SDK.  More specifically, I'd like a verification of the following points:

 

1)  As I understand it, SAPUI5 is already part of the Design Studio framework.  If this is the case, is it correct to assume that we do not need to explicitly load the SAPUI5 libraries by referencing them in the contribution.xml file with a <jsInclude> tag?

 

2) If the SAPUI5 libraries are indeed automatically loaded by the Design Studio framework, which of the libraries are included in Design Studio 1.2 and which version eg. 1.14.0, 1.16.0?  Specifically, is the sap.m mobile library loaded or would I have to explicitly load this if it is needed?

 

Thanks,

 

Mustafa.

 

 


SAP Design Studio 1.4 with SSAS cube

$
0
0

Hi Experts,

 

Am new to SAP Design Studio . We are on SAP BI 4.1 SP5 and have also installed SAP Design Studio 1.4.

We have created our OLAP cubes using SSAS application and have UNX Universes built on these cubes. Am not able to access the OLAP universes from Design Studio. .Am able to access relational universes from Design Studio (these universes are built by connecting to the Sql Server database directly)

 

1.How can I connect to the SSAS cube or universes pointing to the SSAS cube from Design Studio

 

2. Does Design Studio support connecting to a SSAS cube ?

 

Please let me know your thoughts on this.

 

Best Regards,

Rakesh Sudhakar

Cross Domain in Design Studio Client?

$
0
0

Hi everyone,

 

I have an sdk component that uses JQuery ajax function to get data from a web service. The components works correctly when I deploy it to the server. However when I am in the DS Client tool, I cannot see the component or interact with it.

 

I think it is a cross domain issue since it returns localhost as domain but works fine on the server....

 

Is there a setting that I could change in DS Client tool that will allow me to connect to other domain?


Regards,

Garyl


DS YTD

$
0
0


Hi,

 

I would like to know YTD QTD MTD is it possible to create in DS rather than BEX query.

 

In bex query we can do this  but the prompts appears in Design studio, that we don't required only using dropdown in design studio we have to create and should select based on the dropdown and report has charts and cross tab.

 

regards,

 

Ramesh

External JS libraries in SDK component

$
0
0

Hello all,

 

 

I've build a component based on the visJS vizualization library and although it worked perfectly in Design Studio 1.3, it fails to run the external JS file in Design Studio 1.4.

 

My contribution.xml file contains the following line: <jsInclude>res/js/vis.js</jsInclude> which points to a copy of the library available here: http://visjs.org/dist/vis.js

On console.log on the separate file vis is identified as an object and I can instantiate a visualization based on the library. However, when running a Design Studio application using the component I get the following error: Uncaught ReferenceError: vis is not defined

 

Has anyone else had this problem before? I'll be grateful for any suggestion you may have on this topic.

 

 

Thank you,

Alina

DS SDK : Expand hierarchy in visualization

$
0
0

Hello,

 

I'm working my way through some D3 visualizations and have managed to get a tree diagram working thanks to this example:

 

http://www.d3noob.org/2014/01/tree-diagrams-in-d3js_11.html

 

The visualization takes a dimension object with an activated hierarchy and renders it like this:

 

DS_Tree.png

With a crosstab component I can get the tree to expand:

 

DS_Tree_CT.png

 

Now I want to extend this to function like the Collapsible Tree from Mike Bostock:

 

http://bl.ocks.org/mbostock/4339083

 

I've incorporated the transitions from the update function, which all work well, but the problem comes with the click event, which is handled in the D3 code with this function:

 

// Toggle children on click.
functionclick(d) {
  if (d.children) {
  d._children = d.children;
  d.children = null;
  } else {
  d.children = d._children;
  d._children = null;
  }
  update(d);

 

This is called in the update function when the nodes are declared:

 

        // Declare the nodes

        var node = svg.selectAll("g.node")

        .data(nodes)

        .enter().append("g")

        .attr("class", "node")

        .attr("transform", function(d) { return "translate(" + d.y + "," + d.x + ")"; })

        .on("click", click);

 

I can see the event being fired, and d._children being switched with d.children, but nothing happens in my visualization. I even tried modifying the function to set the metadata property nodeState, hoping this would alter the datasource, but to no avail:

 

            function click(d) {

            if (d.children) {

              d._children = d.children;

              d.children = null;

              if (d.nodeState)

              {d.nodeState = "EXPANDED";}

            } else {

              d.children = d._children;

              d._children = null;

              if (d.nodeState)

              {d.nodeState = "COLLAPSED";}

            }

            update(d);

          }

 

In the console, I can see the property d.nodeState change from EXPANDED to COLLAPSED when I set the appropriate break point, but nothing changes in the viz

 

I'm guessing I need to do something differently to interact with the data source and change it's state but I couldn't find anything in the guide. Unfortunately, the Simple Crosstab sample doesn't provide the expand/collapse functionality either, though it does render the plus signs that indicate a hierarchy node is available.

 

Any ideas on how I can add this interactivity to my extension would be very welcome.

 

Thanks,

Jim

Problem Initial View and others

$
0
0

Hi all,

 

recently we updated to DS 1.4 and our BW to 7.4 SP09.

Now we are facing some problems that did not arise before these updates but until now I am not able to exactly determine the reason and therefore I have no idea how to solve these.

 

Maybe one of you have any idea.

 

My first problem is the following:

 

In my application I have serveral datasources. For them you are normally able to select the displayed measures and keyfigures within the "initial view" tab.

Inside this tab it seems to work as normal but when closing it, the view in my application does not change.

It is like DS is not able to save the selected view but I don't understand why.

 

WDesign Studio I get this error message:

 

Could not bind a reference of component com.sap.ip.bi.base.application.DeclaredServiceActivator. The reference is: Reference[name = IActivatorBase, interface = com.sap.ip.bi.base.bundle.IActivatorBase, policy = dynamic, cardinality = 0..n, target = null, bind = addRICActivator, unbind = removeRICActivator]

 

I just looked in the path: C:\Program Files\SAP BusinessObjects\Design Studio\plugins

and there is no such "com.sap.ip.bi.base.application.DeclaredServiceActivator" - should there be one and this is the problem?

 

------------------------------------------------------------

---UPDATE----

I just created a totally new dashboard with only one new Datasource.

Now DesignStudio gives me no error message at all but I still cannot change the shown keyfigures in the initial view tab.

After closing the initial view selection, Design Studio will always show ALL keyfigures from the query in the crosstab.

When using this data source with a chart component, I am able to select the shown keyfigures in the chart poperties.

------------------------------------------------------------

 

 

In other dashboards I had a conversion routine in some queries and now DS is no longer able to load these.

Then I get following messages:

 

eclipse.buildId=@qualifier@

java.version=1.7.0_55

java.vendor=SAP AG

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE

Framework arguments:  BusinessObjects Design Studio

Command-line arguments:  -os win32 -ws win32 -arch x86_64 BusinessObjects Design Studio

 

Error

Mon Jan 12 11:04:21 CET 2015

ERROR [f65382e7-dff1-4a74-8f78-345dc1115107]: Termination message sent

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

ERROR

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

 

com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

ERROR

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:211)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageByListener(MessageManager.java:177)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:129)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:207)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageByListener(MessageManager.java:177)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:129)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:207)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageByListener(MessageManager.java:177)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:129)

    at com.sap.ip.bi.base.application.service.RfcService.fillMessages(RfcService.java:358)

    at com.sap.ip.bi.base.application.service.RfcService.doPostProcessing(RfcService.java:307)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.doPostProcessing(ProviderSelectionObject.java:1817)

    at com.sap.ip.bi.base.application.service.rfcproxy.base.RfcFunction.execute(RfcFunction.java:97)

    at com.sap.ip.bi.base.application.service.RfcService.doPostProcessing(RfcService.java:316)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.doPostProcessing(ProviderSelectionObject.java:1817)

    at com.sap.ip.bi.base.application.service.rfcproxy.base.RfcFunction.execute(RfcFunction.java:97)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderInfoObject.prepareForSelectionMemberAccess(ProviderInfoObject.java:1698)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderComponentList.setup(ProviderComponentList.java:145)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderComponentList.isSingleMemberSelection(ProviderComponentList.java:414)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.selection.ComponentList.isOnlySingleMembersSelection(ComponentList.java:1108)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Sorting.supportsSortBySelection(Sorting.java:457)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Sorting.getType(Sorting.java:208)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Sorting.setSortByMembersPresentation(Sorting.java:251)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSorting(StateDomParser.java:3243)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseQvSorting(StateDomParser.java:3122)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseQvCharacteristicNode(StateDomParser.java:2016)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseCharacteristic(StateDomParser.java:1645)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.CharacteristicList.setStateFromDom(CharacteristicList.java:92)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.readListObjectDetails(StateDomParser.java:4274)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelectorNode(StateDomParser.java:293)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseQueryViewNode(StateDomParser.java:368)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelectorNodeBase(StateDomParser.java:253)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelector(StateDomParser.java:212)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelector(StateDomParser.java:165)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.readStateFromDom(SelectionObject.java:1489)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.setDefaultStateByXml(SelectionObject.java:1627)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.initializeState(SelectionObject.java:718)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QueryView.initializeState(QueryView.java:182)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.initialization(SelectionObject.java:684)

    at com.sap.ip.bi.base.application.impl.ServiceManagement.registerService(ServiceManagement.java:776)

    at com.sap.ip.bi.base.application.impl.ServiceManagement.createService(ServiceManagement.java:397)

    at com.sap.ip.bi.base.application.impl.ServiceManagement.createService(ServiceManagement.java:365)

    at com.sap.ip.bi.base.application.impl.Application.createService(Application.java:491)

    at com.sap.ip.bi.base.application.service.base.BaseServiceDescription.createService(BaseServiceDescription.java:142)

    at com.sap.ip.bi.webapplications.dataproviders.selector.impl.WdpSelector.doInit(WdpSelector.java:325)

    at com.sap.ip.bi.webapplications.runtime.object.page.impl.PageObject.init(PageObject.java:296)

    at com.sap.ip.bi.webapplications.runtime.object.provider.impl.Provider.init(Provider.java:37)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.initPageObject(PageStateProcessor.java:2798)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.setupPageObject(PageStateProcessor.java:2104)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.createPageObject(PageStateProcessor.java:2061)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageCommandProcessor.doCreateDataProviderCommand(PageCommandProcessor.java:819)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.doCreateDataProviderCommand(Page.java:5933)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:606)

    at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:155)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:425)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:340)

    at com.sap.ip.bi.webapplications.runtime.processor.CommunicationProcessor.processCommand(CommunicationProcessor.java:212)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandSuper(Page.java:4910)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommand(Page.java:4476)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommand(Page.java:1)

    at com.sap.ip.bi.web.runtime.template.impl.items.TemplateAssembler.createPageObjects(TemplateAssembler.java:655)

    at com.sap.ip.bi.web.runtime.template.impl.xml.XmlTemplateAssembler.reloadTemplate(XmlTemplateAssembler.java:182)

    at com.sap.ip.bi.web.runtime.template.impl.xml.XmlTemplateAssembler.doInit(XmlTemplateAssembler.java:94)

    at com.sap.ip.bi.web.runtime.template.impl.items.TemplateAssembler.init(TemplateAssembler.java:162)

    at com.sap.ip.bi.webapplications.runtime.impl.object.template.Template.doInit(Template.java:144)

    at com.sap.ip.bi.webapplications.runtime.object.page.impl.PageObject.doInit(PageObject.java:344)

    at com.sap.ip.bi.webapplications.runtime.object.page.impl.PageObject.init(PageObject.java:296)

    at com.sap.ip.bi.webapplications.runtime.rendering.renderer.ItemRenderer.init(ItemRenderer.java:41)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.initPageObject(PageStateProcessor.java:2798)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.setupPageObject(PageStateProcessor.java:2104)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.createPageObject(PageStateProcessor.java:2061)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.setTemplate(Page.java:5440)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageCommandProcessor.doSetTemplateCommand(PageCommandProcessor.java:1698)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.doSetTemplateCommand(Page.java:6028)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:606)

    at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:155)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:443)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:340)

    at com.sap.ip.bi.webapplications.runtime.processor.CommunicationProcessor.processCommand(CommunicationProcessor.java:212)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandSuper(Page.java:4910)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandInternal(Page.java:4569)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandSequence(Page.java:4729)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.doProcessRequest(Page.java:2574)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page._processRequest(Page.java:780)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processRequest(Page.java:5157)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processRequest(Page.java:5150)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller.doProcessRequest(Controller.java:1244)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller._processRequest(Controller.java:1094)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller.processRequest(Controller.java:1060)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller.processRequest(Controller.java:1)

    at com.sap.ip.bi.server.runtime.sevice.impl.BIRuntimeServerService._handleRequest(BIRuntimeServerService.java:524)

    at com.sap.ip.bi.server.runtime.sevice.impl.BIRuntimeServerService.handleRequest(BIRuntimeServerService.java:907)

    at com.sap.ip.bi.server.execution.engine.runtime.LocalBIExecutionService.executeRequest(LocalBIExecutionService.java:47)

    at com.sap.ip.bi.client.execution.AbstractExecutionServlet.handleRequest(AbstractExecutionServlet.java:146)

    at com.sap.ip.bi.client.servlet.BIPrivateServlet.handleRequest(BIPrivateServlet.java:35)

    at com.sap.ip.bi.client.execution.AbstractExecutionServlet.doPost(AbstractExecutionServlet.java:125)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

    at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)

    at org.eclipse.equinox.http.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:38)

    at com.sap.ip.bi.zen.webserver.designer.ZenSessionFilter.doFilter(ZenSessionFilter.java:45)

    at org.eclipse.equinox.http.servlet.internal.FilterRegistration.doFilter(FilterRegistration.java:81)

    at org.eclipse.equinox.http.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:35)

    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:132)

    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

    at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:386)

    at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)

    at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)

    at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:229)

    at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)

    at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)

    at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)

    at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)

    at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)

    at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)

    at org.eclipse.jetty.server.Server.handle(Server.java:370)

    at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)

    at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:982)

    at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1043)

    at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)

    at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)

    at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)

    at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667)

    at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)

    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)

    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)

    at java.lang.Thread.run(Thread.java:812)

 

At the moment most of our dashboards don't work and I am desperately looking for a solution.

 

Regards

 

Steffen

Design Studio 1.2 SDK - including SAPUI5 libraries

$
0
0

Hi,

 

There will be times when it would be beneficial to include SAPUI5 controls within an SDK component, either on the canvas or the additional properties sheet.  In this context, I'd appreciate a clarification and any guidance regarding how to reference SAPUI5 libraries within the Design Studio SDK.  More specifically, I'd like a verification of the following points:

 

1)  As I understand it, SAPUI5 is already part of the Design Studio framework.  If this is the case, is it correct to assume that we do not need to explicitly load the SAPUI5 libraries by referencing them in the contribution.xml file with a <jsInclude> tag?

 

2) If the SAPUI5 libraries are indeed automatically loaded by the Design Studio framework, which of the libraries are included in Design Studio 1.2 and which version eg. 1.14.0, 1.16.0?  Specifically, is the sap.m mobile library loaded or would I have to explicitly load this if it is needed?

 

Thanks,

 

Mustafa.

 

 


Viewing all 1411 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>