Connect Jedox Cloud and Power BI

Connect Jedox Cloud and Power BI

To connect Jedox to Power BI, you will need to follow these steps: Make sure that the oData Hub service is running. (check Cloud Console) Obtain the Jedox OData API URL: usually, add odata before the cloud name. Example https://odata.test-jedox4begginers.cloud.jedox.com/DATABASENAME. It is also essential to add a database name at the end. In our case, we will put Biker as a database. Connect to Jedox from Power BI: Here, click on the "Get Data" button in the Home tab, and select "OData Feed" from the list of available data sources. Paste the Jedox OData API URL into the "URL" field, and click "OK" to connect to the Jedox server. Add the username and password. Depending if your team is using SSO choose Windows or Basic for standard Jedox credentials. Import data into Power BI: Once connected to the Jedox server, you can select the Jedox cubes or views you want to import into Power BI. Select the cube or view from the list of available tables,...
Read More
Running ETLs via macro using REST standard

Running ETLs via macro using REST standard

The Integrator Server SOAP API has been deprecated as of Jedox 2022.4. If you used this standard to run ETL via macros you will need to change it now. There are two ways of doing that: Running ETLS via action buttons (highly recommended) Running ETLs via macro using Rest standard Action buttons are now already well incorporated in many Jedox projects and running ETL via them should be an easy task. However if you have issue to build such a connection, check out this link. Running ETLs using Rest standard takes a bit of coding but nothings super complex. IF you had SOAP connection-build-macro-report, make a backup of it and then delete all the code. Have in mind that if you had any IF or any other statements in the code before, make sure to save them. First we need to call the library require library('integrator-rest'); After that code for running looks like this: function sampleETL() {   $etlProject = "PROJECT NAME";   $etlJob = 'JOB NAME';   // define array...
Read More
Jedox password policy

Jedox password policy

Starting from 2022.2 version Jedox implemented password policy change. That means that users cannot have abc123 passwords. Something more sophisticated should be done. Therefor certain rules needs to be followed: at least 10 characters at least one digit at least one of the symbols !@#$%^&* at least one uppercase or lowercase letter [A-Z] [a-z] cannot contain a period or space Example: Q20J!b5ei0951 This policy can be changed if the company has different set of rules. in that case parameter password-pattern in palo.ini allows you to change the password settings concerning the password length and the password pattern/complexity. Any attempt to change the password that does not match the defined pattern will result in an error displayed in the Change Password dialog. The password pattern can be defined by the key password-pattern <regular_expression>. If the new password does not match the pattern, an error message (error code 1004) is returned. <according to KB>. if in any case you built up the ETL which automatically assign the passwords to newly created users, groovy should look something like this: def user = API.getProperty('user'); def generator = { String alphabet, int...
Read More
How to hide System database to users

How to hide System database to users

System database is vital part of Jedox modeler. It contains all information of users, groups, roles and their interactions in cubes. By default, it is visible by every user with modeler rights. In some environments admin user do not want to make this database visible. In _GROUP_DATABASE_DATA cube is not possible to choose System database, since this cube is in fact in this database and therefor not possible to put N on the group. Workaround will be to play with the Roles for a bit. Usecase is that user should see Modeler, some Databases inside, but not the System. That we can achieve by doing this rule rights: Modeler is Full Access or Read and Rights is no access. Now, when our role is active and updated we should see modeler like this:...
Read More
IOUtils.setByteArrayMaxOverride() issue

IOUtils.setByteArrayMaxOverride() issue

Upgrading to the 2022.2 version brings more perks and features. One of these is also the IOUtils.setByteArrayMaxOverride() issue. Usually, it comes in this type of form and states that the maximum length for this record type is achieved. The fix is very simple. If you have access to the config file it is necessary to add this line: Afterward, you just need to restart the ETL service and you are ready to go. In case you don't have access, please write to Jedox Cloud Support....
Read More
Cube load modes- (Insert, Add, Delete, Update, Create)

Cube load modes- (Insert, Add, Delete, Update, Create)

In my numerous Jedox projects career, I was constantly getting questions related to cube load modes. Although is very well explained in the knowledge base, users frequently asked for clarification. When is a great moment for the update, where for add, and where for delete + insert combination? It is important to start with the type of load modes for the cube: Add - Values from the data source are aggregated and added to the existing values in the cube. Insert - Existing values in the cube are overwritten with the values from the data source. Create - The existing cube is deleted and created anew with the dimension order as defined in the source. Delete- Values from the data source are deleted in the cube. Update - The existing cube is emptied; values from the data source are aggregated and written to the cube. How it practically looks is something which is in the best way explained in the below EXCEL screenshot: Based on this image you...
Read More
License and user activation assignments

License and user activation assignments

Jedox is fastly growing software and with every new version many cool features are released. That brings a bigger market and eventually more customers. Recently many projects are done for big corporations which handle a large number of users. In order to manage and control all of these users and licenses customers frequently ask for some type of report where all this information is displayed. In the below picture, you can see a list of all users split by activity or in other words, are they allowed to use the system or not. As you can see there are possibilities to assign or unassign the license, activate or deactivate the user, and search for them in case the list becomes super long. Speaking of super, take a look at the newest super planning program by Jedox. It is worth mentioning that license assignments can be found in the System database under the _USER_USER_PROPERTIES. More about system cubes can be found on the following...
Read More
How to use hyperlinks in Jedox?

How to use hyperlinks in Jedox?

In a Jedox, a hyperlink (or link) is an item like a word or button that points to another location. When you click on a link, the link will take you to the target of the link, which may be another report, excel document, or other online content. There are two possibilities to create a hyperlink in Hedox: Searching the hyperlink in functions Clicking on the right click and selecting the hyperlink icon Hyperlink function The syntax for the function is HYPERLINK(link_location, friendly_name, screen_tip, source1, destination1[, source2, destination2, …]). link_location - > here we can define where will our link takes us to. It can be on the same page "#SELF", different sheet "[SELF]Sheet2!A1", a particular report "//Demo Spreadsheets/Demos/Bikers Best/Navigation/Bikers Best Navigation" or a web page like "https://jedox4beginners.com/". friendly_name - > How will link the world to the outside world <Link Friendly Name> Tool_tip -> What is visible when covering the link? In case you don't want to see any addresses or strings just...
Read More
Creation and last login time of the Jedox user

Creation and last login time of the Jedox user

In this article we will show you how to pull the report will all your users and their creation and last login time. This could be useful in case you are wondering which of your users actually use Jedox and utilize the "Free seat" license. In case you are interested more in how licensing in Jedox works you can check it out here. As we learned in some of the previous articles details about Users can be found in the System database and _USER_USER_PROPERTIES cube. SO therefore we will paste a view with this information: As you can see both data values are stored in Serial number time of date. Example: =DATEVALUE("01-02-2015") returns Unix time stamp 1420156800, which represents 02-Jan-2015 (=60*60*24*16437 seconds since 1.1.1970). Obviously, we will need to convert these values into something more readable. There are two ways to do it: Convert from UNIX to normal date using excel formula =(A1/86400)+DATE(1970,1,1) Option to convert the value with Rule. For this option, I suggest...
Read More
Code: 1 – element not found : unspecified default write element in the dimension

Code: 1 – element not found : unspecified default write element in the dimension

In this article, we will explain what the following error message means and how to deal with it: Code: 1 - element not found : unspecified default write element in dimension This error appears when the user wants to extend his cube with an additional dimension. The problem is that system doesn't know to which element to assign already existing data. If the dimension which needs to be added has more than 1 element that is where the confusion starts. In the below example, we will show how to deal with it. Like always we will use the Demo database: Dimension country is the one which should be added and extend Sales cube. As stated in the error message, there is a necessity to proclaim one default write element so all the data is assigned to it. We can do it here: In the picture above we assigned the element Europe as the Default Write Element. After this action, saving the changed layout of the...
Read More