Wednesday, 27 May 2020
  2 Replies
  2.8K Visits
0
Votes
Undo

Sometimes I receive LandFX CAD files from a subcontractor in a zip file.  When I open his files and load the lfx file (FX_PROJECTFILES --> Restore --> Import), and then regenerate the irrigation schedule (Irrigation Schedule --> Regenerate YES --> Select specific schedule for a work area), if there are multiple irrigation schedules for multiple work areas, the legend doesn't appear to connect correctly to the work area and instead reloads the schedule as reflecting the entire project.  If I create a new legend and click on the work area, it functions correctly.

So the work area is recognized as valid if I create a new legend, but the schedule he created from it before it got to me seems to have lost it's association.

Accepted Answer
1
Votes
Undo

Julie,

 

In order to speed the querying of work areas in a drawing, the system only looks on the assigned work area layer.  So in this case, your consultant has a different layer configured in their Preferences.

The easiest fix, is to just rename their work area layer to your standard.  Alternately, you could bring in their Preferences as well, which you really would only need to do once, then speeding the process of opening and re-generating in the future.

 

--J

4 years ago
·
#3650
0
Votes
Undo

Ah of course, that makes sense.  He's got some issues with other items in his preferences and I'd rather not have the same, so I'll look into renaming instead.  Thanks Jeremiah!

Accepted Answer
1
Votes
Undo

Julie,

 

In order to speed the querying of work areas in a drawing, the system only looks on the assigned work area layer.  So in this case, your consultant has a different layer configured in their Preferences.

The easiest fix, is to just rename their work area layer to your standard.  Alternately, you could bring in their Preferences as well, which you really would only need to do once, then speeding the process of opening and re-generating in the future.

 

--J

  • Page :
  • 1
There are no replies made for this post yet.