Planning Analytics

 View Only
  • 1.  PAfE API - Limitations for Control objects

    Posted 7 days ago

    Hello everyone,

    Is anyone aware of the limitations of the PAfE API  - Introduction – PAx API - that prevents working with control objects?  I have tried to create a custom report using MDX. For common cubes it works quite well. For control objects (like }ClientGroups) it does not work. It says that the cube not found. On the other hand, I am able to work with the control objects in the PAfE left pane and open it with no problem.

    I have checked the restapi log and there is no API call to the TM1 server during the VBA call. 

    Few details:

    • MDX was copied from PAW editor to avoid typos.
    • 32bit version of PAfE, v99

    Thanks for your help in advance, Filip



    ------------------------------
    Filip Rufer
    ------------------------------


  • 2.  RE: PAfE API - Limitations for Control objects

    Posted 2 days ago
    Edited by Saif Ali Sabri 2 days ago

    My response was crafted with AI assistance, tailored to provide detailed and actionable guidance for your query.  

    It seems like you're running into a problem when trying to work with control objects (like }ClientGroups) in the IBM PAfE API (PAx API), particularly when using MDX in a custom report. You're able to access and interact with these control objects in the PAfE left pane, but when trying to use them in your custom report via MDX, the system is returning an error stating that the cube cannot be found.

    Here are a few possible reasons and limitations you might be encountering when working with control objects in the PAfE API:

    1. Control Objects and Cubes Are Different Entities

    • Control objects like }ClientGroups are metadata objects, not regular data cubes. The PAfE API and MDX typically work with cubes that hold data (such as actual sales figures or forecast data). Control objects, on the other hand, define the structure or configuration of the system.
    • These objects are not "cubes" and thus, when you attempt to query them using MDX, the system might not recognize them in the same way it does for regular data cubes.

    2. MDX Limitations

    • MDX (Multidimensional Expressions) is used for querying data within cubes and is designed to work with data rather than metadata (like control objects).
    • If you're attempting to query a control object such as }ClientGroups, the API may not support the querying of these types of objects with MDX, as MDX is intended for data retrieval rather than metadata manipulation.

    You may need to use different methods for interacting with control objects, such as:

    • PAfE API functions that directly interact with metadata or configuration objects.
    • TM1 REST API calls to interact with control objects in a more direct way.

    3. API Call Visibility in Logs

    • You mentioned that there are no API calls being logged when you make the VBA call to the TM1 server. This could be because the VBA code isn't triggering an actual TM1 server query. This could happen if the query or the object you're trying to access is being incorrectly referenced or if the PAfE API is not properly set up to initiate that request.

    Double-check your API call to ensure you're correctly specifying the cube or object you're querying. Also, ensure that the TM1 server is properly configured to allow access to the control objects you're working with.

    4. Control Object Accessibility in PAfE

    • Control objects, such as }ClientGroups, can be accessed in the PAfE left pane because the PAfE client is specifically designed to interact with these objects in a user-friendly manner. However, interacting with them programmatically through the PAfE API might have some limitations depending on how the system is configured and what API methods are available.
    • Ensure that your API calls are correctly formatted for interacting with these objects. If they are metadata objects, they may require special handling through the API.

    5. TM1 Server Configuration

    • Check the configuration of your TM1 server to ensure that the control objects are accessible via the PAfE API. In some cases, the server might have specific permissions or access settings that prevent certain objects (such as }ClientGroups) from being queried programmatically, even though they are visible and accessible within the PAfE client.

    Recommendations:

    1. Use the PAfE API for Metadata: If you're trying to work with metadata or control objects (like }ClientGroups), look for specific PAfE API methods that deal with metadata retrieval rather than using MDX for data cubes.
    2. Check the TM1 REST API: If you're looking for more flexibility in interacting with control objects, the TM1 REST API might offer more direct access to metadata, including control objects.
    3. Debugging: Enable more detailed logging or debugging on the TM1 server to see if any API calls are being attempted and to check for any errors or permissions issues.

    By using the appropriate API methods and ensuring your system is correctly configured, you should be able to resolve this issue.



    ------------------------------
    Saif Ali Sabri
    ------------------------------