Automate

Alright fellow WSers, I need your guidance again. 

I have a repeating table, where I add inputs via a button. The rule counts rows and adds a row if needed. This button is in multiple workflow steps. What I am finding, is when the last input in the table aligns with the material # which is adding ​more rows, the new rows are open for edit. If the material # doesn't align with the last row​, the new rows are NOT open for edits for the amount of rows where the material #s do not align. (see screenshots). 

There is a rule that says if certain criteria are met based on the view, then the rows should be enabled for edit. So, as long as that criteria is met (the data points are added when the new row is added), the new rows should be editable. ​

The rule that determines if the rows are editable or not, is set at view load. I have tried adding this same rule to the button with the hopes that it will retrigger, however it does not. I have tried using a rule that adds blank rows, then another that deletes them after all new rows have been added, but since the # of blank rows needed varies, that's not effective. ​

What am I missing?


------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------

Hi Vanessa

Looks like you're building a great solution! :)

I am not sure I follow all of what is happening in your scenario.  Here's what I note:

• You have rules that populate a repeating table
• You have rules that make rows editable or not editable
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?

My best guess - if something should happen on a row level to make it editable or not, then I believe the rules should be triggered on the row - not on form load or outside of the table - except when copying values into a table.  So you can try to pick a field in the row to apply your editable/not editable rules and see if that helps.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA
------------------------------

Original Message:
Sent: 09-30-2020 12:32
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Alright fellow WSers, I need your guidance again.

I have a repeating table, where I add inputs via a button. The rule counts rows and adds a row if needed. This button is in multiple workflow steps. What I am finding, is when the last input in the table aligns with the material # which is adding ​more rows, the new rows are open for edit. If the material # doesn't align with the last row​, the new rows are NOT open for edits for the amount of rows where the material #s do not align. (see screenshots).

There is a rule that says if certain criteria are met based on the view, then the rows should be enabled for edit. So, as long as that criteria is met (the data points are added when the new row is added), the new rows should be editable. ​

The rule that determines if the rows are editable or not, is set at view load. I have tried adding this same rule to the button with the hopes that it will retrigger, however it does not. I have tried using a rule that adds blank rows, then another that deletes them after all new rows have been added, but since the # of blank rows needed varies, that's not effective. ​

What am I missing?

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------

Hi Sigrid,
It is quite a solution, 2yrs in the making at that!

• You have rules that populate a repeating table
  • Correct
• You have rules that make rows editable or not editable
  • Correct
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?
  • I just used this as reference to show that it wasn't the same, and therefore should not have been disabled. 

The reason I have the view perform the enable/disable on the tables is I wasn't able to get it to happen properly at the table level. Once I moved it to the view, it worked marvelously. Now my issue is getting it to continue to show the proper rows enabled when new rows are added. I added the table specific part of the view rule to a field w/in the table that holds the inputs, but that didn't work. I am thinking that I may have to add another helper field in the table to house the view rules. Instead of using the fields the populate the info. I'll set that up in the AM, fingers crossed that it works.

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------

Original Message:
Sent: 10-01-2020 10:02
From: Sigrid Kok
Subject: Add Rows, View Issue

Hi Vanessa

Looks like you're building a great solution! :)

I am not sure I follow all of what is happening in your scenario.  Here's what I note:

• You have rules that populate a repeating table
• You have rules that make rows editable or not editable
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?

My best guess - if something should happen on a row level to make it editable or not, then I believe the rules should be triggered on the row - not on form load or outside of the table - except when copying values into a table.  So you can try to pick a field in the row to apply your editable/not editable rules and see if that helps.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA

Original Message:
Sent: 09-30-2020 12:32
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Alright fellow WSers, I need your guidance again.

I have a repeating table, where I add inputs via a button. The rule counts rows and adds a row if needed. This button is in multiple workflow steps. What I am finding, is when the last input in the table aligns with the material # which is adding ​more rows, the new rows are open for edit. If the material # doesn't align with the last row​, the new rows are NOT open for edits for the amount of rows where the material #s do not align. (see screenshots).

There is a rule that says if certain criteria are met based on the view, then the rows should be enabled for edit. So, as long as that criteria is met (the data points are added when the new row is added), the new rows should be editable. ​

The rule that determines if the rows are editable or not, is set at view load. I have tried adding this same rule to the button with the hopes that it will retrigger, however it does not. I have tried using a rule that adds blank rows, then another that deletes them after all new rows have been added, but since the # of blank rows needed varies, that's not effective. ​

What am I missing?

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------

I have the add row views now showing correctly. I ended up having to use a trigger for each specific scenario. When there were multiple scenarios on a single trigger, there were still issues. Thank you both again for your help getting through this one. :)

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------

Original Message:
Sent: 10-05-2020 17:07
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Hi Sigrid,
It is quite a solution, 2yrs in the making at that!

• You have rules that populate a repeating table
  • Correct
• You have rules that make rows editable or not editable
  • Correct
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?
  • I just used this as reference to show that it wasn't the same, and therefore should not have been disabled. 

The reason I have the view perform the enable/disable on the tables is I wasn't able to get it to happen properly at the table level. Once I moved it to the view, it worked marvelously. Now my issue is getting it to continue to show the proper rows enabled when new rows are added. I added the table specific part of the view rule to a field w/in the table that holds the inputs, but that didn't work. I am thinking that I may have to add another helper field in the table to house the view rules. Instead of using the fields the populate the info. I'll set that up in the AM, fingers crossed that it works.

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader

Original Message:
Sent: 10-01-2020 10:02
From: Sigrid Kok
Subject: Add Rows, View Issue

Hi Vanessa

Looks like you're building a great solution! :)

I am not sure I follow all of what is happening in your scenario.  Here's what I note:

• You have rules that populate a repeating table
• You have rules that make rows editable or not editable
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?

My best guess - if something should happen on a row level to make it editable or not, then I believe the rules should be triggered on the row - not on form load or outside of the table - except when copying values into a table.  So you can try to pick a field in the row to apply your editable/not editable rules and see if that helps.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA

Original Message:
Sent: 09-30-2020 12:32
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Alright fellow WSers, I need your guidance again.

I have a repeating table, where I add inputs via a button. The rule counts rows and adds a row if needed. This button is in multiple workflow steps. What I am finding, is when the last input in the table aligns with the material # which is adding ​more rows, the new rows are open for edit. If the material # doesn't align with the last row​, the new rows are NOT open for edits for the amount of rows where the material #s do not align. (see screenshots).

There is a rule that says if certain criteria are met based on the view, then the rows should be enabled for edit. So, as long as that criteria is met (the data points are added when the new row is added), the new rows should be editable. ​

The rule that determines if the rows are editable or not, is set at view load. I have tried adding this same rule to the button with the hopes that it will retrigger, however it does not. I have tried using a rule that adds blank rows, then another that deletes them after all new rows have been added, but since the # of blank rows needed varies, that's not effective. ​

What am I missing?

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------

Well, I was wrong, it works as long as the form hasn't been moved forward by any of the other tasks. If it has, then the additional tasks, that use the same table, do not see the additional row added by the previous task. So, when a new row is added by the current task, it's not see that a row was added by a previous task. 

This table is part several tasks, where all tasks need to be completed in order for the form to move to the next task. 

Is there some sort of table rendering I need to do at form load so that it captures all current details? I'm not sure if emptying/reloading the table is the answer.  Help!

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------

Original Message:
Sent: 10-14-2020 08:15
From: Vanessa Kutasi
Subject: Add Rows, View Issue

I have the add row views now showing correctly. I ended up having to use a trigger for each specific scenario. When there were multiple scenarios on a single trigger, there were still issues. Thank you both again for your help getting through this one. :)

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader

Original Message:
Sent: 10-05-2020 17:07
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Hi Sigrid,
It is quite a solution, 2yrs in the making at that!

• You have rules that populate a repeating table
  • Correct
• You have rules that make rows editable or not editable
  • Correct
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?
  • I just used this as reference to show that it wasn't the same, and therefore should not have been disabled. 

The reason I have the view perform the enable/disable on the tables is I wasn't able to get it to happen properly at the table level. Once I moved it to the view, it worked marvelously. Now my issue is getting it to continue to show the proper rows enabled when new rows are added. I added the table specific part of the view rule to a field w/in the table that holds the inputs, but that didn't work. I am thinking that I may have to add another helper field in the table to house the view rules. Instead of using the fields the populate the info. I'll set that up in the AM, fingers crossed that it works.

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader

Original Message:
Sent: 10-01-2020 10:02
From: Sigrid Kok
Subject: Add Rows, View Issue

Hi Vanessa

Looks like you're building a great solution! :)

I am not sure I follow all of what is happening in your scenario.  Here's what I note:

• You have rules that populate a repeating table
• You have rules that make rows editable or not editable
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?

My best guess - if something should happen on a row level to make it editable or not, then I believe the rules should be triggered on the row - not on form load or outside of the table - except when copying values into a table.  So you can try to pick a field in the row to apply your editable/not editable rules and see if that helps.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA

Original Message:
Sent: 09-30-2020 12:32
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Alright fellow WSers, I need your guidance again.

I have a repeating table, where I add inputs via a button. The rule counts rows and adds a row if needed. This button is in multiple workflow steps. What I am finding, is when the last input in the table aligns with the material # which is adding ​more rows, the new rows are open for edit. If the material # doesn't align with the last row​, the new rows are NOT open for edits for the amount of rows where the material #s do not align. (see screenshots).

There is a rule that says if certain criteria are met based on the view, then the rows should be enabled for edit. So, as long as that criteria is met (the data points are added when the new row is added), the new rows should be editable. ​

The rule that determines if the rows are editable or not, is set at view load. I have tried adding this same rule to the button with the hopes that it will retrigger, however it does not. I have tried using a rule that adds blank rows, then another that deletes them after all new rows have been added, but since the # of blank rows needed varies, that's not effective. ​

What am I missing?

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------

Original Message:
Sent: 10-15-2020 15:45
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Well, I was wrong, it works as long as the form hasn't been moved forward by any of the other tasks. If it has, then the additional tasks, that use the same table, do not see the additional row added by the previous task. So, when a new row is added by the current task, it's not see that a row was added by a previous task.

This table is part several tasks, where all tasks need to be completed in order for the form to move to the next task.

Is there some sort of table rendering I need to do at form load so that it captures all current details? I'm not sure if emptying/reloading the table is the answer.  Help!

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader

Original Message:
Sent: 10-14-2020 08:15
From: Vanessa Kutasi
Subject: Add Rows, View Issue

I have the add row views now showing correctly. I ended up having to use a trigger for each specific scenario. When there were multiple scenarios on a single trigger, there were still issues. Thank you both again for your help getting through this one. :)

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader

Original Message:
Sent: 10-05-2020 17:07
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Hi Sigrid,
It is quite a solution, 2yrs in the making at that!

• You have rules that populate a repeating table
  • Correct
• You have rules that make rows editable or not editable
  • Correct
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?
  • I just used this as reference to show that it wasn't the same, and therefore should not have been disabled. 

The reason I have the view perform the enable/disable on the tables is I wasn't able to get it to happen properly at the table level. Once I moved it to the view, it worked marvelously. Now my issue is getting it to continue to show the proper rows enabled when new rows are added. I added the table specific part of the view rule to a field w/in the table that holds the inputs, but that didn't work. I am thinking that I may have to add another helper field in the table to house the view rules. Instead of using the fields the populate the info. I'll set that up in the AM, fingers crossed that it works.

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader

Original Message:
Sent: 10-01-2020 10:02
From: Sigrid Kok
Subject: Add Rows, View Issue

Hi Vanessa

Looks like you're building a great solution! :)

I am not sure I follow all of what is happening in your scenario.  Here's what I note:

• You have rules that populate a repeating table
• You have rules that make rows editable or not editable
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?

My best guess - if something should happen on a row level to make it editable or not, then I believe the rules should be triggered on the row - not on form load or outside of the table - except when copying values into a table.  So you can try to pick a field in the row to apply your editable/not editable rules and see if that helps.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA

Original Message:
Sent: 09-30-2020 12:32
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Alright fellow WSers, I need your guidance again.

I have a repeating table, where I add inputs via a button. The rule counts rows and adds a row if needed. This button is in multiple workflow steps. What I am finding, is when the last input in the table aligns with the material # which is adding ​more rows, the new rows are open for edit. If the material # doesn't align with the last row​, the new rows are NOT open for edits for the amount of rows where the material #s do not align. (see screenshots).

There is a rule that says if certain criteria are met based on the view, then the rows should be enabled for edit. So, as long as that criteria is met (the data points are added when the new row is added), the new rows should be editable. ​

The rule that determines if the rows are editable or not, is set at view load. I have tried adding this same rule to the button with the hopes that it will retrigger, however it does not. I have tried using a rule that adds blank rows, then another that deletes them after all new rows have been added, but since the # of blank rows needed varies, that's not effective. ​

What am I missing?

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------

Hi Vanessa

Sorry you're running into issues with the table between views.

It would be difficult to tell what is happening without looking at the solution as a whole, which could take considerable time and is a bit beyond the type of help the community typically can offer.

It may be time to (1) open a support ticket or (2) engage with our services team or a partner to assist.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA
------------------------------

Original Message:
Sent: 10-15-2020 16:22
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Some screenshots in case they help.

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader

Original Message:
Sent: 10-15-2020 15:45
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Well, I was wrong, it works as long as the form hasn't been moved forward by any of the other tasks. If it has, then the additional tasks, that use the same table, do not see the additional row added by the previous task. So, when a new row is added by the current task, it's not see that a row was added by a previous task.

This table is part several tasks, where all tasks need to be completed in order for the form to move to the next task.

Is there some sort of table rendering I need to do at form load so that it captures all current details? I'm not sure if emptying/reloading the table is the answer.  Help!

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader

Original Message:
Sent: 10-14-2020 08:15
From: Vanessa Kutasi
Subject: Add Rows, View Issue

I have the add row views now showing correctly. I ended up having to use a trigger for each specific scenario. When there were multiple scenarios on a single trigger, there were still issues. Thank you both again for your help getting through this one. :)

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader

Original Message:
Sent: 10-05-2020 17:07
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Hi Sigrid,
It is quite a solution, 2yrs in the making at that!

• You have rules that populate a repeating table
  • Correct
• You have rules that make rows editable or not editable
  • Correct
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?
  • I just used this as reference to show that it wasn't the same, and therefore should not have been disabled. 

The reason I have the view perform the enable/disable on the tables is I wasn't able to get it to happen properly at the table level. Once I moved it to the view, it worked marvelously. Now my issue is getting it to continue to show the proper rows enabled when new rows are added. I added the table specific part of the view rule to a field w/in the table that holds the inputs, but that didn't work. I am thinking that I may have to add another helper field in the table to house the view rules. Instead of using the fields the populate the info. I'll set that up in the AM, fingers crossed that it works.

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader

Original Message:
Sent: 10-01-2020 10:02
From: Sigrid Kok
Subject: Add Rows, View Issue

Hi Vanessa

Looks like you're building a great solution! :)

I am not sure I follow all of what is happening in your scenario.  Here's what I note:

• You have rules that populate a repeating table
• You have rules that make rows editable or not editable
• I don't understand the material number alignment part.  How does this factor in the rules triggering properly?

My best guess - if something should happen on a row level to make it editable or not, then I believe the rules should be triggered on the row - not on form load or outside of the table - except when copying values into a table.  So you can try to pick a field in the row to apply your editable/not editable rules and see if that helps.

Best Regards,
Sigrid

------------------------------
Sigrid Kok
PSE | Winshuttle NA

Original Message:
Sent: 09-30-2020 12:32
From: Vanessa Kutasi
Subject: Add Rows, View Issue

Alright fellow WSers, I need your guidance again.

I have a repeating table, where I add inputs via a button. The rule counts rows and adds a row if needed. This button is in multiple workflow steps. What I am finding, is when the last input in the table aligns with the material # which is adding ​more rows, the new rows are open for edit. If the material # doesn't align with the last row​, the new rows are NOT open for edits for the amount of rows where the material #s do not align. (see screenshots).

There is a rule that says if certain criteria are met based on the view, then the rows should be enabled for edit. So, as long as that criteria is met (the data points are added when the new row is added), the new rows should be editable. ​

The rule that determines if the rows are editable or not, is set at view load. I have tried adding this same rule to the button with the hopes that it will retrigger, however it does not. I have tried using a rule that adds blank rows, then another that deletes them after all new rows have been added, but since the # of blank rows needed varies, that's not effective. ​

What am I missing?

------------------------------
Vanessa Kutasi | Application Analyst II
IDEXX | New England WUG Leader
------------------------------