Hi Benjamin,
Thank you so much, your suggestion worked. I have another follow up question I need your advice on.
I made the above changes in the below place
<maximo-datasource id="numericDomainDS" lookup-data="true" object-structure="MXAPINUMERICDOMAIN" offline-immediate-download="true" page-size="10" selection-mode="single">
<schema id="xcyyb1">
<attribute id="e7zb_" name="domainid" searchable="true"/>
<attribute id="jx2nx" name="value" searchable="true" sub-type="INTEGER"/>
<attribute id="q8vbz" name="description" searchable="true"/>
</schema>
<code-comment text="Adding domain for internal priority of ticket" id="jzg77"/>
<maximo-datasource-override id="internalPriorityList" mobile-qbe-filter="{{'domainid': '=TICKETPRIORITY'}}" where="domainid="TICKETPRIORITY""/>
<maximo-datasource-override id="numericDomainValidationDS"/>
</maximo-datasource>
If you notice I changed the attribute sub type in the numericDomainDS datasource, although I am using the overriden datasource which is internalPriorityList for the lookup.
Now the issue is that this numericDomainDS I believe is being used in the TicketSpec table to display numeric domains against the classification attributes (which allows decimals). Since we changed the type here it will impact the display of spec attributes numeric domain values as well.
So do you recommend creating a separate data source altogether for the internalpriority numeric domain where I can specify schema and sub-type without impacting the numericDomainDS?
------------------------------
Invading Moss
N/A
------------------------------
Original Message:
Sent: 12-29-2024 04:47
From: Benjamin Alterauge
Subject: Query regarding create service request customization in maximo mobile
Have you tried setting the value attribute to an integer in the datasource?
...<attribute name="value" searchable="true" sub-type="INTEGER" id="test1"/>...
------------------------------
Benjamin Alterauge
SPIE RODIAS GmbH
------------------------------