Vikas さんのグループアクティビティ

REST API does not return properties with Item datatype

Vikas — Thu, 27 Jul 2023 06:49:25 GMT

Hi,

I am using Release 15 and trying to GET all Properties of an Item using REST API with this request:

http://server/innovatorserver/server/odata/par('D193004BBD7D4EF390925A859A4E371D')

It does return all properties except the ones which are datatype = Item.

I am able to get the missing items properties one-by-one with such requests:

http://server/innovatorserver/server/odata/par('D193004BBD7D4EF390925A859A4E371D')/lead_est

I tried with other ItemTypes as well and find same issue.

Is this normal for OData or I am missing something in the API request? Or may be newer version has this issue fixed already?

Of course AML requests do return all properties though.

Regards

Calling SearchDialog from Server method

Vikas — Fri, 03 Feb 2023 07:51:39 GMT

Hi,

Is it possible to show SearchDialog from a Server method? I can use MaximazableDialog in Javascript to show the SearchDialog and get the response in callback. But I want to use such facility in a Server method.

In my particular case, I am trying to send email using a server method. If the Recipent is already entered then it sends the email. But I want to prompt the user to search for another user item when Recipient is not pre-defined.

If that is not possible then any alternative suggestions will be appreciated.

Kind Regards,

Vikas

Decimal and Float precision, rounding and overflow errors

david.creech — Fri, 30 Jul 2021 15:28:54 GMT

I am looking for a solution to the following problems that I am encountering using 12.0 SP9 with Float and Decimal data types.

I need to store engineering data that can contain very large and very small numbers. In testing a property using the Float and Decimal types I find that both have problems storing the full precision that SQL Server supports.

For Float, large numbers work as expected from -1.79E+308 to +1.79E+308. However small numbers do not. The smallest number that I can store in a Float property from the Aras item's form is 1E-20. I can not store any more digits of precision (for example, 1.000000000000001E-20), either entering the value in scientific or decimal notation.

Using MS SQL Server Management Studio I can manually edit the item to store smaller numbers in the database (down to the minimum of 2.23E-308). However these are rounded to 0 in Aras.

As an aside, despite the documentation and training saying that you need to specify Precision and Scale for floats, neither of these appear to have any effect on how the Float column is specified in SQL Server - it always uses the default 8 byte float size.

For Decimal there are problems with precision, rounding and large numbers. Here Precision and Scale really do matter, as they should. For Precision of 38 and Scale of 0, I should be able to store values up to 10^38-1 = 99999999999999999999999999999999999999, and I can do this directly in SQL. However Aras gives a Conversion Overflow error in search grids and the item form if this is stored in the database. The largest number that Aras can handle is 79228162514264330000000000000. This happens to be 2^96 rounded to 16 digits of precision. If Scale > 0 is specified the largest number possible is reduced.

Aras only seems to be able to store 16 or sometimes 17 precise digits in the Decimal type with Precision set to 38, and the rounding behavior is inconsistent. For example entering 11111111111111111 rounds up (!) to 11111111111111112 when the item is saved. 1111111111111111111 also rounds up to 1111111111111111200, but 1111111111111111100 rounds down to 1111111111111111000.

My best guess is that Aras is performing internal conversions that result in the rounding and overflow problems, since using SQL Server directly works as expected.

Is this a known bug? Is there any way to work around this behavior? Do later service packs fix these issues?

Thanks

Dynamic Dropdown Error

Vikas — Wed, 06 Jul 2022 09:47:01 GMT

Hi,

I am using example in https://community.aras.com/b/english/posts/tech-tip-dynamically-change-type-ahead-english/ for dynamically populating values for a dropdown at OnFocus event.

The form works fine as far as a value is selected from the dropdown. But if no value is selected in the dropdown and the dropdown loses focus, an error appears that 'Value entered does not exist for (so-n-so). Edit again?'

Can anyone please advise what am I missing here?

Vikas

Ask A Question I

Wed, 06 Jul 2022 02:39:22 GMT

Ask a question in a forum.

Unlock Item using REST API

gautamk — Wed, 07 Oct 2020 07:44:37 GMT

Hello,

Consider the scenario

1. User A has locked the Document from Innovator GUI and edited Name property but did not Save, unlock and Close

2. Same user using REST API (through Postman, does not matter though) unlock the Item. Rest call as below

PATCH: http://<hostname>/odata/Document('8B07D4B0D3AF4376BC031336E2E0E216')

{

"@aras.action" : "unlock"

}

The response status is 200 ok.

3. Try to unlock Item again by firing the same REST API: Status 500 Internal Server Error "ItemIsNotLockedException" which is considering #2 above. This indicates Item is not locked.

4. Go to Innovator UI and access Item ( In this case above Document ), UI shows up Document as "Locked". Refresh, logout have no impact. Status on UI is "Locked". Even I cannot Unlock, "Save Unlock and Close" from Innovator UI for this Item.

I would like to know

1. What is the problem in this scenario and why there is the discrepancy in REST API and Innovator UI behavior

2. Why dont "@aras.action" : "unlock" checks if the document is in edit stage and not to unlock in this case

3. How to fetch the lock status of an Item using REST API. Instead of using locked_by_id property of Document Item Type

Any help / suggestions are greatly appreciated

- Gautam