Forward effective call number typeId property

RCA Group

None

Description

Forward the effectiveCallNumberComponents.typeId property from inventory storage.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Bohdan SuprunJanuary 9, 2020 at 9:44 AM

Closing as dev only. Verified on the snapshot.

Bohdan SuprunDecember 13, 2019 at 10:22 AM

Waiting for to be merged.

Bohdan SuprunDecember 11, 2019 at 3:09 PM

Bohdan SuprunDecember 11, 2019 at 10:34 AM

Hi All,

Will proceed with just ID then, we can raise a separate issue in case we will have a problem with lookup on UI side.

Bohdan SuprunDecember 10, 2019 at 2:25 PM

,

I don't really follow: the description talks only about forwarding the typeId field but your comment refers to the type's name field.

My understanding that the callNumber typeId property will be included to the Effective call number string that we have on item (am I correct understand ?). And because of this we need the call number type's name to display it, but backend will return the type ID only. My question was, does it make sense to include name together with Id on backend side, or it is fine to lookup this on UI side (so backend will send just type ID).

, yes the typeId is on item record. And you will have to call /call-number-types?query=id==<id> to get the whole record with name.

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Prokopovych

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created December 10, 2019 at 12:35 PM
Updated March 9, 2020 at 1:30 PM
Resolved January 9, 2020 at 9:45 AM
TestRail: Cases
TestRail: Runs