Connector Improvement: Create key between STOPS and STOP_CAUSES
AnsweredHi,
This is regarding the Factbird connector.
I would like to request additional columns for the Stop and StopCause entity. I've attached a screenshot which highlights all columns that I would like to include (red are critical, yellow are nice to have).
Additionally, it is very important to be able to match stopCauses and Stops. It should be possible to get the links between these two entities with the following query:
query Lines {
lines(languageCode: "en", filter: { lineName: "L07" }) {
id
languageCode
owner
name
description
mainPeripheralId
batches {
nextToken
count
pages
items {
batchId
batchNumber
plannedStart
actualStart
actualStop
amount
comment
lineId
state
manualScrap
produced
tags
sorting
plannedEtc
actualEtc
stops {
_id
originalStart
ongoing
duration
comment
initials
registeredTime
isMicroStop
isAutomaticRegistration
countermeasure
countermeasureInitials
stopCause {
_id
id
stopType
categoryId
categoryName
name
description
order
requireInitials
requireComment
deleted
languageCode
legacyStopCauseId
enableCountermeasure
}
}
}
}
}
}

-
Official comment
Hi Ari,
I'm pleased to inform you that the feature request for creating a key between the STOPS and STOP_CAUSES entities in the Factbird connector is live. If you have any questions or need further assistance, please don't hesitate to reach out.
Best,
Sanjeevv Maniram T
Please sign in to leave a comment.
Comments
1 comment