eventKey

[simmy]

In the epc_calendar table in my MySQL database is an eventKey field which is unpopulated could this field be used to tag for instance an asset_id for an event so that the event could be called from the Assets page as a planned maintenance event. If so how does one go about populating the eventKey field?

[ve9gra]

The simple answer is no.

The longer answer is that custom fields is a feature that is being considered (worked on) for a future revision/version. Note that this does not mean that the field could be used in the way you're describing.

Alternatively, one way that you could tackle this without requiring anything custom would be to make use of the categories system.

Simply create a sub-category called "Asset", and populate the selections with all your assets. Then when creating an event, you'll be able to select the asset. Then from the asset page, you can use the $showCat variable to limit the display of events to only ones that have that asset selected. This will work well if you only assign a single asset per event.

In the case where multiple assets could be selected, then you would have to create a sub-category for each asset, and have a single selection for each. The selection could be "Yes" or "Reserved" or "Assigned", etc... Then from the asset page, you'd use the same technique as above.

[simmy]

thanks for the response - cant see how to create a sub-category - and with my existing assets numbering 1000's it would not be possible to enter them again as my database already has an assets register with each asset having a unique id and it would be a nightmare trying to sync two sets of asset id's. What i was looking for was to use epc as a scheduler for asset maintenance.

"Note that this does not mean that the field could be used in the way you're describing"

How would / could this field be populated?

[ve9gra]

I am not the developer, so I cannot speak to how a potential feature may be implemented. I have no knowledge of if, how, or when it will be released.

That was just my caveat.

[Brian]

That field is for future use (when in the future, I'm not sure).

You can use it if you wish, just be sure to check the change logs to make sure we didn't start using it if you upgrade.