-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛: Workorder MCCR tab: Checklists is missing #621
Comments
The logic in CustomAPI_WorkOrderChecklists (the api used to show MCCRs) filters out all tags which are not lci tags. What Atle is saying seems to be the case. CustomAPI views are owned and maintained by FAM. @Gustav-Eikaas |
@aman-riaz can you add projectSchema to Custom_WorkOrderChecklist view? |
I have discussed this with Magnus, and need some more context from @Gustav-Eikaas on what was discussed with regards to adding projectSchema to the view. Notes: See https://famapi.equinor.com/index.html for comparing the models. One solution would be to add the missing fields to the Custom_WorkOrderChecklist |
@aman-riaz Is it possible for you to add the missing fields so we can switch to the other view and close this view? |
Custom_WorkOrderChecklist_v1 now ready in FAM-api with new fields. I suggest when you fetch the data, set a filter if possible to "Custom_WorkOrderChecklist_v1 .FormularGroup = "MCCR". This way you can only fetch the subset of data necessary for this purpose. mccrType = FormularType |
@aman-riaz the new view is missing MechanicalCompletionPackageUrlId and CommissioningPackageUrlId in order to create links to ProCoSys. Can these fields be added to the view Custom_WorkOrderChecklist_v1? |
This issue is on hold until https://github.com/equinor/fusion-data-gateway/issues/545 is ready |
Description
Some workorders is missing MCCRs in projectportal.
Could it be because the checklists are connected to dummy-tags?
Reproduce
Open Workorder app on OGP project
Open workorder: 25588400
Expected behavior
Number of checklists should match ProCoSys
The text was updated successfully, but these errors were encountered: